Triple
T21152777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiefs-in-Assembly |
E521233
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of the Assembly of First Nations |
C13942
|
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: component of the Assembly of First Nations Context triple: [Chiefs-in-Assembly, instanceOf, component of the Assembly of First Nations]
-
A.
First Nations tribal council
A First Nations tribal council is a governing body composed of representatives from one or more Indigenous communities that makes collective decisions on political, social, economic, and cultural matters affecting their people.
-
B.
Métis leader
A Métis leader is an individual of Métis heritage who guides and advocates for the political, cultural, and social interests of Métis communities.
-
C.
indigenous peoples' organization
chosen
An indigenous peoples' organization is a collective entity formed and led by indigenous communities to represent their rights, interests, cultures, and self-determined development at local, national, or international levels.
-
D.
federally recognized tribe
A federally recognized tribe is a Native American or Alaska Native governing body that the U.S. federal government formally acknowledges as a sovereign political entity with a government-to-government relationship and eligibility for specific legal rights, services, and protections.
-
E.
Nlaka'pamux band government
The Nlaka'pamux band government is the local Indigenous governing body responsible for administering the affairs, lands, programs, and services of a specific Nlaka'pamux First Nation community.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:58 p.m.