Triple
T32531286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mixtecan |
E831461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the Otomanguean language family |
C12029
|
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: branch of the Otomanguean language family Context triple: [Mixtecan, instanceOf, branch of the Otomanguean language family]
-
A.
Oto-Manguean language branch
The Oto-Manguean language branch is a large and diverse family of indigenous Mesoamerican languages, primarily spoken in Mexico, known for complex tonal systems and significant internal variation.
-
B.
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.
-
C.
branch of the Chibchan language family
A branch of the Chibchan language family is a subgroup of related Chibchan languages that share a common ancestral origin and distinctive linguistic features within the broader family.
-
D.
subfamily of Tupian languages
A subfamily of Tupian languages is a smaller, genetically related group of languages within the larger Tupian family that share a more recent common ancestor and distinctive linguistic features.
-
E.
Oto-Manguean language
chosen
An Oto-Manguean language is a member of a large, diverse family of indigenous Mesoamerican languages, primarily spoken in Mexico, characterized by complex tonal systems and significant grammatical and phonological variation.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:01 a.m.