Triple
T34075275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South West Native Title Settlement |
E873890
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous land use agreement |
C12618
|
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 use agreement Context triple: [South West Native Title Settlement, instanceOf, Indigenous land use agreement]
-
A.
Indigenous land rights document
chosen
A formal record that asserts, defines, or protects the legal and customary rights of Indigenous peoples to their traditional lands, territories, and resources.
-
B.
Aboriginal land council
An Aboriginal land council is a representative body established to advocate for, manage, and protect the land rights, cultural heritage, and interests of Aboriginal communities within a defined region.
-
C.
indigenous territory
An indigenous territory is a geographically defined area traditionally inhabited, used, or managed by an Indigenous people, where they maintain cultural, spiritual, social, and often legal relationships to the land and its resources.
-
D.
Indigenous–Crown treaties in Canada
Indigenous–Crown treaties in Canada are formal agreements between Indigenous nations and the British Crown (and later the Canadian state) that define relationships, land use, rights, and mutual obligations, forming a foundational legal and political framework for the country.
-
E.
Aboriginal reserve
An Aboriginal reserve is a tract of land set aside by a government for the use and occupation of Indigenous peoples, typically recognized as a distinct community with certain self-governing rights and cultural protections.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.