Triple
T35249023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adnyamathanha Traditional Lands Association |
E1018044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous land council |
C12794
|
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 council Context triple: [Adnyamathanha Traditional Lands Association, instanceOf, Indigenous land council]
-
A.
Aboriginal land council
chosen
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.
-
B.
First Nations tribal council
A First Nations tribal council is a governing body composed of representatives from one or more Indigenous communities that makes collective decisions on political, social, economic, and cultural matters affecting their people.
-
C.
Aboriginal community organisation
An Aboriginal community organisation is a locally governed, Aboriginal-controlled entity that delivers culturally grounded services, advocacy, and programs to support the social, economic, and cultural wellbeing of Aboriginal people and communities.
-
D.
Indigenous elders council
A group of respected senior members of an Indigenous community who provide cultural guidance, wisdom, and leadership in decision-making and governance.
-
E.
Indigenous co-management body
An Indigenous co-management body is a collaborative governance entity in which Indigenous communities and state or other institutional partners share authority, responsibility, and decision-making over lands, waters, or resources.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.