Triple
T7730485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koya |
E175235
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Gondi language |
E144000
|
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: Gondi language | Statement: [Koya, relatedTo, Gondi language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gondi language Context triple: [Koya, relatedTo, Gondi language]
-
A.
Gondi language
chosen
The Gondi language is a Dravidian language spoken by the indigenous Gond people of central India, written in multiple scripts including Telugu and Devanagari.
-
B.
Kumaoni language
Kumaoni language is an Indo-Aryan language of the Central Pahari group spoken primarily in the Kumaon region of Uttarakhand, India.
-
C.
Gonja language
The Gonja language is a Gur language spoken primarily by the Gonja people in northern Ghana.
-
D.
Baigani language
Baigani language is an indigenous Indo-Aryan language spoken by the Baiga people of central India, particularly in parts of Madhya Pradesh and Chhattisgarh.
-
E.
Angika language
Angika language is an Eastern Indo-Aryan language spoken primarily in parts of Bihar and Jharkhand in India, known for its close relation to Maithili and its rich regional literary tradition.
- 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_69c6995e912c81909a49a2657103f786 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c703358cf881909df8496d943d6de7 |
completed | March 27, 2026, 10:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8b52e176481908595fea4ace7a607 |
completed | March 29, 2026, 5:14 a.m. |
Created at: March 27, 2026, 4:06 p.m.