Triple
T34075274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South West Native Title Settlement |
E873890
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | native title 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: native title settlement Context triple: [South West Native Title Settlement, instanceOf, native title settlement]
-
A.
native title legislation
Native title legislation comprises the body of laws and regulations that recognize, define, and govern the land and resource rights of Indigenous peoples based on their traditional laws and customs.
-
B.
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.
-
C.
native title activist
A native title activist is an individual who advocates for the recognition, protection, and enforcement of Indigenous peoples’ traditional land rights and interests under native title law.
-
D.
Aboriginal title case
An Aboriginal title case is a legal proceeding in which Indigenous peoples seek judicial recognition and protection of their inherent land rights based on traditional occupation and use, rather than on grants from the state.
-
E.
native title determination
A native title determination is a formal legal decision by a court or tribunal that recognizes whether and to what extent Indigenous peoples’ traditional rights and interests in land or waters are legally acknowledged under native title 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.