Triple
T6561526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tzeltalan branch |
E153793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of Mayan languages |
C21585
|
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 Mayan languages Context triple: [Tzeltalan branch, instanceOf, branch of Mayan languages]
-
A.
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.
-
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.
Penutian languages subgroup
The Penutian languages subgroup is a proposed family of Native American languages, primarily spoken in western North America, that are hypothesized to share a common ancestral origin based on structural and lexical similarities.
-
D.
Oto-Manguean language
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.
-
E.
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.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 1:52 p.m.