Triple
T35896241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern O’odham varieties |
E1038232
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southern Uto-Aztecan language variety |
C64597
|
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: Southern Uto-Aztecan language variety Context triple: [Southern O’odham varieties, instanceOf, Southern Uto-Aztecan language variety]
-
A.
Chinantecan language variety
A Chinantecan language variety is a specific linguistic form within the Chinantecan branch of the Oto-Manguean language family, characterized by its own phonological, lexical, and grammatical features used by a particular Chinantecan-speaking community.
-
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.
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.
-
D.
Chinantecan language
The Chinantecan language is a group of closely related indigenous Otomanguean languages spoken by the Chinantec people in the northern highlands of Oaxaca, Mexico.
-
E.
Totonac language variety
A Totonac language variety is a specific regional or social form of the Totonac language, distinguished by its unique phonological, lexical, and grammatical features within the broader Totonacan language family.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.