Triple
T12987155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazaribagh |
E321797
|
entity |
| Predicate | regionalLanguage |
P237
|
FINISHED |
| Object | Nagpuri |
E301323
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Nagpuri | Statement: [Hazaribagh, regionalLanguage, Nagpuri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nagpuri Context triple: [Hazaribagh, regionalLanguage, Nagpuri]
-
A.
Nagpuri
chosen
Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
-
B.
Kurukh
Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
-
C.
Bagheli
Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
-
D.
Mirpuri
Mirpuri is a major dialect of the Lahnda (Western Punjabi) language, primarily spoken in the Mirpur region of Azad Kashmir and among its diaspora communities.
-
E.
Gojri
Gojri is an Indo-Aryan language traditionally spoken by the Gujjar community across parts of northern India and Pakistan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e5f47ec8190b39107bc016f9824 |
completed | April 10, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c0f95c548190a6fc2c1ea98246c3 |
completed | May 3, 2026, 3:28 a.m. |
Created at: April 9, 2026, 8:41 p.m.