Triple
T19908335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty 6 |
E478477
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | agreement between the Canadian Crown and First Nations |
C566
|
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: agreement between the Canadian Crown and First Nations Context triple: [Treaty 6, instanceOf, agreement between the Canadian Crown and First Nations]
-
A.
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.
-
B.
Aboriginal rights case
An Aboriginal rights case is a legal proceeding that addresses claims by Indigenous peoples to inherent or treaty-based rights, such as land, resources, self-governance, or cultural practices, and determines how those rights are recognized and protected under state law.
-
C.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
D.
medieval political agreement
A medieval political agreement is a formal or informal pact between rulers, nobles, or institutions that defines mutual obligations—such as protection, allegiance, tribute, or territorial control—within the feudal and dynastic power structures of the Middle Ages.
-
E.
Indigenous land rights document
A formal record that asserts, defines, or protects the legal and customary rights of Indigenous peoples to their traditional lands, territories, and resources.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:53 p.m.