Triple
T8724485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlapanecan languages |
E207096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indigenous Mesoamerican languages |
C24974
|
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: indigenous Mesoamerican languages Context triple: [Tlapanecan languages, instanceOf, indigenous Mesoamerican languages]
-
A.
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.
-
B.
Mixe–Zoquean language
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.
-
C.
branch of Mayan languages
A branch of Mayan languages is a subgroup within the Mayan language family consisting of closely related languages that share a common ancestral origin and distinctive linguistic features.
-
D.
subgroup of Mayan languages
A subgroup of Mayan languages is a set of closely related Mayan languages that share a common ancestral branch within the Mayan language family, characterized by shared phonological, grammatical, and lexical innovations.
-
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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.