Triple
T22961487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainland Comox |
E570910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Coast Salish language variety |
C35353
|
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: Coast Salish language variety Context triple: [Mainland Comox, instanceOf, Coast Salish language variety]
-
A.
Chinookan language variety
A Chinookan language variety is a specific form or dialect of the Chinookan language family traditionally spoken by Indigenous Chinookan peoples of the Pacific Northwest, characterized by its own phonological, grammatical, and lexical features.
-
B.
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.
-
C.
Indigenous language variety of Canada
An Indigenous language variety of Canada is a distinct linguistic system or dialect traditionally spoken by First Nations, Inuit, or Métis communities within the territory now known as Canada, reflecting unique cultural, historical, and geographic identities.
-
D.
Indigenous language variety
chosen
An Indigenous language variety is a distinct form or dialect of a language traditionally spoken by an Indigenous community, reflecting its unique cultural, historical, and social practices.
-
E.
Chinookan language
Chinookan language is a family of Native American languages traditionally spoken by the Chinook peoples of the Pacific Northwest along the lower Columbia River.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:47 p.m.