Triple
T37605851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yawuru Park Council |
E935649
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint management body |
C50695
|
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: joint management body Context triple: [Yawuru Park Council, instanceOf, joint management body]
-
A.
joint management arrangement
A joint management arrangement is a structured agreement in which two or more parties share authority, responsibilities, and decision-making over a specific resource, project, or organization.
-
B.
joint organization
A joint organization is a collaborative entity formed by two or more independent parties that share resources, responsibilities, and decision-making to achieve common objectives.
-
C.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
D.
partnership body
A partnership body is an organized group formed by two or more independent entities that collaborate under agreed arrangements to pursue shared goals, responsibilities, and benefits.
-
E.
Indigenous co-management body
chosen
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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.