Triple
T32925446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aboriginal and Torres Strait Islander leaders |
E842259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous leaders in Australia |
C61464
|
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 leaders in Australia Context triple: [Aboriginal and Torres Strait Islander leaders, instanceOf, Indigenous leaders in Australia]
-
A.
Aboriginal Australian alliance
An Aboriginal Australian alliance is a cooperative relationship or coalition formed between different Aboriginal Australian groups, communities, or organizations to pursue shared cultural, political, social, or land-related goals.
-
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 people of Queensland
Indigenous people of Queensland are the Aboriginal and Torres Strait Islander communities whose diverse cultures, languages, and traditions are rooted in the lands and waters of what is now the Australian state of Queensland.
-
D.
Australian Aboriginal language community
An Australian Aboriginal language community is a group of Aboriginal people connected by shared traditional language, cultural practices, and ancestral ties to specific Country within Australia.
-
E.
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.
- F. None of above. chosen
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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.