Triple
T11304823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nlaka’pamux Nation Tribal Council member bands |
E267687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | First Nations government collective |
C8668
|
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 government collective Context triple: [Nlaka’pamux Nation Tribal Council member bands, instanceOf, First Nations government collective]
-
A.
tribal nation
A tribal nation is a sovereign Indigenous community recognized as a distinct political and cultural entity with its own government, territory, and traditions.
-
B.
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.
-
C.
Indigenous representative body proposal
A structured plan or framework outlining the creation, role, and operation of a formal body that represents Indigenous peoples in political, legal, or policy decision-making processes.
-
D.
Aboriginal land council
An Aboriginal land council is a representative body established to advocate for, manage, and protect the land rights, cultural heritage, and interests of Aboriginal communities within a defined region.
-
E.
tribal confederation
chosen
A tribal confederation is a loose alliance of distinct tribes that cooperate for mutual defense, governance, or shared interests while retaining their individual identities and autonomy.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.