Triple
T20753251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatchet Lake Denesuline First Nation |
E510785
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous government in Canada |
C38433
|
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: Indigenous government in Canada Context triple: [Hatchet Lake Denesuline First Nation, instanceOf, Indigenous government in Canada]
-
A.
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.
-
B.
Indian Act
The Indian Act is a Canadian federal law that governs the status, rights, and administration of First Nations peoples and communities, historically enabling extensive government control and assimilation policies.
-
C.
First Nations tribal council
chosen
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.
-
D.
indigenous state in the Americas
An indigenous state in the Americas is a politically organized society whose governing institutions, territorial control, and cultural foundations are rooted in and led by Native peoples of the Western Hemisphere, historically or in the present.
-
E.
Inuit-governed region
An Inuit-governed region is a geographically defined area where Inuit people exercise primary political authority and self-determination over local governance, land use, and cultural affairs.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:34 p.m.