Triple
T2961551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Popoluca |
E80060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mixe–Zoquean language |
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: Mixe–Zoquean language Context triple: [Popoluca, instanceOf, Mixe–Zoquean language]
-
A.
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.
-
B.
Uto-Aztecan language
A Uto-Aztecan language is a member of a Native American language family spoken from the western United States through northern and central Mexico, sharing common ancestral linguistic features despite diverse cultures and regions.
-
C.
Quechuan language
A Quechuan language is any member of a family of indigenous languages of the Andes, primarily spoken in Peru, Bolivia, Ecuador, Colombia, and Argentina, that share common grammatical structures and vocabulary derived from a Proto-Quechuan ancestor.
-
D.
Southern Athabaskan language
A Southern Athabaskan language is a member of the Athabaskan branch of the Na-Dené language family spoken primarily in the Southwestern United States and northern Mexico, characterized by complex verb morphology and tonal or pitch-accent features.
-
E.
Uto-Aztecan language branch
The Uto-Aztecan language branch is a family of Indigenous languages spread from the western United States through northern and central Mexico, including well-known languages such as Nahuatl, Hopi, and Ute.
- F. None of above. chosen
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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:57 p.m.