Triple
T5809356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koya Gondi |
E128827
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Gondi language |
C16754
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: variety of Gondi language Context triple: [Koya Gondi, instanceOf, variety of Gondi language]
-
A.
Gondi language variety
chosen
A Gondi language variety is a specific regional or social form of the Gondi language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Dravidian language continuum.
-
B.
variety of Fang language
A variety of Fang language is a specific regional or social form of the Fang language distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Fang forms.
-
C.
variety of Sindhi
A variety of Sindhi is a distinct form or dialect of the Sindhi language characterized by unique phonological, lexical, and grammatical features associated with a particular region, community, or social group.
-
D.
variety of Punjabi language
A variety of Punjabi language is a distinct regional or social form of Punjabi characterized by unique phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with other Punjabi forms.
-
E.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
- F. None of above.
Provenance (1 batch)
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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:52 p.m.