Triple
T14315352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tukwila band |
E354941
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Coast Salish subgroup |
C10784
|
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 subgroup Context triple: [Tukwila band, instanceOf, Coast Salish subgroup]
-
A.
Coast Salish people
chosen
The Coast Salish people are Indigenous peoples of the Pacific Northwest Coast, encompassing numerous related nations who share distinct Coast Salish languages, cultural traditions, and ancestral territories in what is now Washington State and British Columbia.
-
B.
Kalapuya subgroup
The Kalapuya subgroup is a division within the Kalapuya people, an Indigenous group of the Willamette Valley in Oregon, distinguished by shared linguistic, cultural, and territorial characteristics.
-
C.
Haida community
A Haida community is a social and cultural group of Haida people, traditionally located in Haida Gwaii and parts of Southeast Alaska, bound together by shared language, kinship, governance, and land-based practices.
-
D.
Nlaka’pamux communities
Nlaka’pamux communities are Indigenous groups in the interior of British Columbia, Canada, who share a common Nlaka’pamux language, culture, and traditional territory along the Fraser and Thompson Rivers, while maintaining distinct local governance and social structures.
-
E.
Tsimshian community
A Tsimshian community is a social and cultural group of Tsimshian people, traditionally organized in coastal villages of the Pacific Northwest, who share common language, kinship systems, governance, and ceremonial practices.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:12 a.m.