Triple
T35887460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern O’odham varieties |
E1037689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | O’odham language variety |
C37222
|
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: O’odham language variety Context triple: [Northern O’odham varieties, instanceOf, O’odham language variety]
-
A.
Yavapai language variety
A Yavapai language variety is a specific form or dialect of the Yavapai language, distinguished by unique phonological, lexical, or grammatical features used by a particular Yavapai-speaking community.
-
B.
Oʼodham language
chosen
The Oʼodham language is a Uto-Aztecan language spoken by the Tohono Oʼodham and Akimel Oʼodham peoples of the Sonoran Desert region in the southwestern United States and northern Mexico, characterized by rich oral traditions and a complex verb system.
-
C.
Cahuilla language variety
Cahuilla language variety refers to any distinct regional or social form of the Cahuilla language, reflecting variations in pronunciation, vocabulary, and usage among Cahuilla-speaking communities.
-
D.
Mazatec language variety
A Mazatec language variety is a specific regional or social form of the Mazatec language, characterized by distinct phonological, lexical, and grammatical features within the broader Mazatecan linguistic continuum.
-
E.
Mazahua language variety
A Mazahua language variety is a specific regional or social form of the Mazahua language, characterized by distinct phonological, lexical, and grammatical features within the broader Mazahua linguistic continuum.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.