Triple
T37331682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gomeroi Native Title Applicant |
E926767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | native title applicant group |
C10029
|
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 applicant group Context triple: [Gomeroi Native Title Applicant, instanceOf, native title applicant group]
-
A.
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.
-
B.
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.
-
C.
native title body corporate
A native title body corporate is an Indigenous-owned legal entity established to hold, manage, and protect native title rights and interests on behalf of a native title group after a determination is made.
-
D.
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.
-
E.
user group
chosen
A user group is a collection of users who share common permissions, roles, or characteristics within a system, enabling collective management and access control.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.