Triple
T19369860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanda Gondi |
E484502
|
entity |
| Predicate | relatedTo |
P37
|
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: [Chanda Gondi, relatedTo, Adilabad Gondi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adilabad Gondi Context triple: [Chanda Gondi, relatedTo, 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.
Balangiri dialect
The Balangiri dialect is a regional variety of the Koshali language spoken primarily in and around the Balangir area of western Odisha, India.
-
C.
Gōṇḍī
Gōṇḍī is a South-Central Dravidian language spoken primarily by the Gondi people in central India.
-
D.
Chhindwara Gondi
Chhindwara Gondi is a regional variety of the Gondi language spoken primarily by Gondi communities in and around the Chhindwara district of central India.
-
E.
Kurukh
Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619af33e481908643f8beb2f498dc |
completed | April 20, 2026, 12:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a072b7a688481908155907db993b589 |
completed | May 15, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:35 p.m.