Triple
T6398544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gondi language |
E144000
|
entity |
| Predicate | hasDialects |
P4251
|
FINISHED |
| Object | Adilabad Gondi |
E111782
|
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: Adilabad Gondi | Statement: [Gondi language, hasDialects, Adilabad Gondi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adilabad Gondi Context triple: [Gondi language, hasDialects, Adilabad Gondi]
-
A.
Adilabad Gondi
chosen
Adilabad Gondi is a regional dialect of the Gondi language spoken by Gondi communities in and around the Adilabad area of India.
-
B.
Kurukh
Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
-
C.
Nagpuri
Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
-
D.
Aheri Gondi
Aheri Gondi is a regional variety of the Southern Gondi language spoken by Gondi communities in parts of central India.
-
E.
Andhratharhi
Andhratharhi is a town located in the Madhubani district of the Indian state of Bihar.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06897ebc48190842d48cce469eba5 |
completed | March 22, 2026, 10:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6389bd9f48190af9811cf8cee124e |
completed | March 27, 2026, 7:58 a.m. |
Created at: March 22, 2026, 4:35 p.m.