Triple
T5322489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nishnawbe Aski Nation communities |
E121706
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | First Nations communities |
C12907
|
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: First Nations communities Context triple: [Nishnawbe Aski Nation communities, instanceOf, First Nations communities]
-
A.
indigenous community
chosen
An indigenous community is a group of people with historical continuity to pre-colonial or original inhabitants of a region, maintaining distinct cultural, social, and political traditions tied to their ancestral lands and identities.
-
B.
Inuit community
An Inuit community is a group of Indigenous Arctic peoples who share close-knit social ties, traditional subsistence practices, and cultural heritage adapted to life in polar environments.
-
C.
Coast Salish people
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.
-
D.
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.
-
E.
tribal people
Tribal people are communities that maintain distinct cultural, social, and often linguistic identities, typically rooted in ancestral lands and traditional ways of life that differ from dominant national societies.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:59 p.m.