Named Entity Recognition (batch)

Extract entities from up to 64 multilingual texts in one request.

POST/api/models/ner/batch

Related NOSIBLE resources

research & data

Explore the NOSIBLE World interface, inspect the World data dictionary, and browse the classification ontologies used by World.

Authorizations

Bearer

Authorizationstringrequiredheader

Required Bearer API key. Programmatic access to the World API needs a key; browsing nosible.world in a browser does not.

Example: Bearer nos_sk_...

Body

application/json

textsstring[]requiredbody

Between 1 and 64 texts, each at most 8,000 characters.

Example: ["NVIDIA opened a new office in Johannesburg.","SAP expanded in Berlin."]

thresholdnumberbody

Entity confidence threshold from 0 to 1. Defaults to 0.6.

Example: 0.6

How to use this endpoint

guidance

Use the batch route when you have several independent texts. Submit between 1 and 64 texts; the result order matches the input order. Each result preserves its source text so entity offsets remain unambiguous.

Response body

application/json

These are the fields you can build against. Nested names use dot notation; optional sections are called out in their descriptions.

resultsobject[]

One extraction result per input text, in the same order as texts.

Example: [{ "text": "SAP expanded in Berlin.", "entities": [{ "start": 0, "end": 3, "text": "SAP", "label": "ORG", "score": 0.98 }] }]

results[].textstring

The exact corresponding input text.

Example: SAP expanded in Berlin.

results[].entitiesobject[]

Detected entities with half-open character offsets, fixed labels, and scores.

Example: [{ "start": 0, "end": 3, "text": "SAP", "label": "ORG", "score": 0.98 }]

model_provenance.nerstring

NER checkpoint used by the model service.

Example: NOSIBLE/gliner-ner-v1

Responses and errors

HTTP

200Request succeeded. The response body is shown in the panel on the right.

400invalid_request — The request is syntactically valid JSON but a value, date, filter, or combination of fields is invalid.

401unauthorized — The required API key or Bearer credential is missing or invalid.

422validation_error — The request shape is understood but one or more values fail validation.

429rate_limited — The request exceeded the account or public-window rate limit. Respect Retry-After when supplied.

502upstream_error — An upstream retrieval service failed while processing the request.

504upstream_timeout — An upstream retrieval service did not respond within the request timeout.