Triple
T33842253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buku-Larrnggay Mulka Centre |
E867387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous-owned organisation |
C37920
|
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-owned organisation Context triple: [Buku-Larrnggay Mulka Centre, instanceOf, Indigenous-owned organisation]
-
A.
Aboriginal-owned organisation
chosen
An Aboriginal-owned organisation is an entity that is majority-owned, controlled, and governed by Aboriginal people, operating to advance their cultural, social, and economic interests.
-
B.
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.
-
C.
Indigenous healing organization
An Indigenous healing organization is a community-based entity that provides culturally grounded, land- and tradition-informed wellness, recovery, and support services led by Indigenous knowledge keepers and practices.
-
D.
Indigenous-led program
An Indigenous-led program is an initiative designed, governed, and implemented by Indigenous peoples, grounded in their knowledge systems, priorities, and self-determined goals.
-
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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.