Triple
T6398547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gondi language |
E144000
|
entity |
| Predicate | hasDialects |
P4251
|
FINISHED |
| Object | Koya Gondi |
E128827
|
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: Koya Gondi | Statement: [Gondi language, hasDialects, Koya Gondi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koya Gondi Context triple: [Gondi language, hasDialects, Koya Gondi]
-
A.
Koya Gondi
chosen
Koya Gondi is a dialect of the Gondi language spoken primarily by the Koya tribal communities in central India.
-
B.
Koya
Koya is a Dravidian language spoken primarily by the Koya tribal communities in parts of central and southern India.
-
C.
Manikonda
Manikonda is a rapidly developing residential and IT suburb in the western part of Hyderabad, known for its proximity to major technology hubs and corporate campuses.
-
D.
Kundagannada
Kundagannada is a regional dialect of the Kannada language spoken primarily in the coastal districts of Karnataka, India.
-
E.
Hogenakkal
Hogenakkal is a small town in Tamil Nadu, India, known as the gateway to the famous Hogenakkal Falls on the Kaveri River.
- 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.