Triple
T1728466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oto-Manguean languages |
E37554
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mesoamerican language family |
C1357
|
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: Mesoamerican language family Context triple: [Oto-Manguean languages, instanceOf, Mesoamerican language family]
-
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.
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.
Andean language
An Andean language is any of the indigenous languages historically spoken in the Andean region of South America, such as Quechua and Aymara, characterized by rich agglutinative morphology and deep cultural significance.
-
D.
Native American language
chosen
A Native American language is any of the indigenous languages historically and currently spoken by the Native peoples of the Americas, each embodying unique cultural knowledge, traditions, and worldviews.
-
E.
Algonquian language
An Algonquian language is any member of a family of Indigenous languages of North America, historically spoken from the Atlantic coast to the Great Plains and characterized by complex morphology and polysynthetic structure.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.