Triple
T10778402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Coast Athabaskan |
E254254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Athabaskan language group |
C5728
|
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: Athabaskan language group Context triple: [Pacific Coast Athabaskan, instanceOf, Athabaskan language group]
-
A.
Athabaskan-speaking people
chosen
Athabaskan-speaking people are Indigenous groups of North America whose diverse cultures and communities are linked by related Athabaskan (Dene) languages spread across Alaska, northwestern Canada, and the American Southwest.
-
B.
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.
-
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.
Siouan-speaking people
Siouan-speaking people are Indigenous groups of North America historically and presently united by their use of languages from the Siouan language family, encompassing diverse tribes such as the Sioux, Crow, and Osage.
-
E.
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.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:16 p.m.