Triple
T31614368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1990 Oka Crisis |
E806716
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous land rights conflict |
C50624
|
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 land rights conflict Context triple: [1990 Oka Crisis, instanceOf, Indigenous land rights conflict]
-
A.
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.
-
B.
land rights movement
A land rights movement is a collective social and political effort by communities and their allies to secure legal recognition, control, and equitable access to land and its resources, often challenging historical dispossession and structural inequality.
-
C.
Indigenous rights concept
An Indigenous rights concept is a framework recognizing the inherent collective and individual rights of Indigenous peoples to self-determination, land, culture, governance, and resources, grounded in their distinct historical, spiritual, and legal relationships to their territories.
-
D.
land dispute
chosen
A land dispute is a conflict between parties over the ownership, boundaries, use, or rights associated with a specific piece of land or real property.
-
E.
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.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:38 p.m.