Triple
T35555586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inuvialuit Final Agreement |
E1027483
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | comprehensive land claim settlement |
C34207
|
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: comprehensive land claim settlement Context triple: [Inuvialuit Final Agreement, instanceOf, comprehensive land claim settlement]
-
A.
land claims settlement
chosen
A land claims settlement is a formal agreement that resolves disputes over land ownership or use rights, typically between governments and Indigenous or local communities, through compensation, land transfers, or legal recognition of rights.
-
B.
land claim organization
A land claim organization is an entity that represents individuals or groups in asserting, negotiating, and managing legal or customary rights to specific lands and related resources.
-
C.
land claim area
A land claim area is a geographically defined region over which an individual, group, or entity asserts legal or traditional rights to ownership, use, or control of the land and its resources.
-
D.
land grant
A land grant is a legal conveyance by which a government or authority transfers ownership or usage rights of a specific parcel of land to an individual, organization, or institution, often for settlement, development, or public purposes.
-
E.
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.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.