Triple
T4026780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Cocopa |
E83609
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cocopa language variety |
C13871
|
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: Cocopa language variety Context triple: [Mexican Cocopa, instanceOf, Cocopa language variety]
-
A.
Yavapai language variety
A Yavapai language variety is a specific form or dialect of the Yavapai language, distinguished by unique phonological, lexical, or grammatical features used by a particular Yavapai-speaking community.
-
B.
Chibchan language
A Chibchan language is a member of a family of indigenous languages spoken primarily in Central America and northern South America, characterized by shared grammatical and phonological features reflecting a common ancestral origin.
-
C.
Nicobarese language variety
A Nicobarese language variety is a specific linguistic form or dialect within the Nicobarese branch of the Austroasiatic language family, spoken by the indigenous Nicobarese people of India’s Nicobar Islands.
-
D.
Mixe–Zoquean language
chosen
A Mixe–Zoquean language is a member of a small family of indigenous Mesoamerican languages spoken primarily in southern Mexico, characterized by complex verb morphology and tonal or pitch-accent systems.
-
E.
Central Tano language
A Central Tano language is a member of the Tano branch of the Niger-Congo language family spoken primarily in Ghana and neighboring regions, characterized by tonal phonology and shared grammatical and lexical features with related Akanic and Guang languages.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:36 p.m.