Triple
T12310317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secwepemctsín |
E293458
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Interior Salish language |
C15371
|
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: Interior Salish language Context triple: [Secwepemctsín, instanceOf, Interior Salish language]
-
A.
Tsimshianic language
A Tsimshianic language is any member of a small family of Indigenous languages of the Pacific Northwest Coast of North America, traditionally spoken by the Tsimshian peoples of British Columbia and Alaska.
-
B.
Salishan language
chosen
A Salishan language is any member of a family of indigenous languages spoken primarily in the Pacific Northwest of North America, characterized by complex consonant systems and rich morphological structures.
-
C.
Southern Wakashan language
A Southern Wakashan language is a member of the southern branch of the Wakashan language family, traditionally spoken by Indigenous peoples of the Pacific Northwest Coast, particularly on Vancouver Island and adjacent mainland areas.
-
D.
Cordilleran language
A Cordilleran language is a member of a proposed subgroup of the Austronesian language family spoken in the Cordillera mountain region of northern Luzon in the Philippines, characterized by shared phonological, lexical, and grammatical features distinct from neighboring language groups.
-
E.
Haida language
Haida language is an isolate Indigenous language of the Haida people of Haida Gwaii (Canada) and Prince of Wales Island (Alaska), known for its complex phonology and endangered status.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.