Triple
T12067984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haisla |
E287348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northern Wakashan language |
C19185
|
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: Northern Wakashan language Context triple: [Haisla, instanceOf, Northern Wakashan language]
-
A.
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.
-
B.
Wakashan language
chosen
A Wakashan language is a member of a small family of Indigenous languages spoken primarily along the Pacific Northwest Coast of North America, characterized by complex consonant systems and rich morphological structure.
-
C.
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.
-
D.
Salishan language
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.
-
E.
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.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:48 p.m.