Triple
T36259887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Tonto |
E892050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Apache dialect |
C10973
|
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: Western Apache dialect Context triple: [Southern Tonto, instanceOf, Western Apache dialect]
-
A.
Southern Athabaskan language
chosen
A Southern Athabaskan language is a member of the Athabaskan branch of the Na-Dené language family spoken primarily in the Southwestern United States and northern Mexico, characterized by complex verb morphology and tonal or pitch-accent features.
-
B.
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.
-
C.
Arapaho language
The Arapaho language is an Algonquian language traditionally spoken by the Arapaho people of the Great Plains, now primarily in Wyoming and Oklahoma, and is the focus of ongoing revitalization efforts.
-
D.
Western Apache group
A Western Apache group is a regional social and cultural subdivision of the Apache peoples of the American Southwest, sharing closely related language varieties, kinship ties, and traditional lifeways within a specific territory.
-
E.
Pueblo language
A Pueblo language is any of the indigenous languages historically and presently spoken by the Pueblo peoples of the Southwestern United States, each with distinct linguistic structures and cultural significance.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.