Triple
T17537111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Official Languages Act of Nunavut |
E427089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nunavut legislation |
C9044
|
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: Nunavut legislation Context triple: [Official Languages Act of Nunavut, instanceOf, Nunavut legislation]
-
A.
settlement in Nunavut
A settlement in Nunavut is a small, often remote community within Canada's northern territory, typically characterized by predominantly Inuit populations, limited infrastructure, and reliance on local resources and traditional lifestyles.
-
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.
region of Nunavut
A region of Nunavut is a large administrative and geographic subdivision of the Canadian territory of Nunavut, encompassing multiple communities and vast Arctic land and marine areas for governance, service delivery, and statistical purposes.
-
D.
Act of Parliament of Canada
chosen
An Act of Parliament of Canada is a law formally enacted by the Parliament of Canada, consisting of the House of Commons, the Senate, and the Crown, that establishes or amends legal rules applicable within Canada.
-
E.
self-determination legislation
Self-determination legislation comprises laws and legal frameworks that recognize, protect, and regulate the right of peoples or groups to autonomously determine their political status, governance, and development.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:49 a.m.