Triple
T33842990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Local Aboriginal Land Council |
E867403
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community-controlled organisation |
C20591
|
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: community-controlled organisation Context triple: [Metropolitan Local Aboriginal Land Council, instanceOf, community-controlled organisation]
-
A.
community organisation
chosen
A community organisation is a structured group of people who collaborate locally to address shared needs, interests, or issues and to improve the well-being of their community.
-
B.
community-driven initiative
A community-driven initiative is a collaborative effort led and shaped by local stakeholders who identify needs, design solutions, and take collective action to improve their shared environment or well-being.
-
C.
peer-led organization
A peer-led organization is a group or institution in which individuals with shared experiences or statuses collectively govern, make decisions, and provide services or support without reliance on traditional hierarchical authority.
-
D.
self-governing organization
A self-governing organization is an entity that independently establishes and enforces its own rules, structures, and decision-making processes without external control.
-
E.
multistakeholder organization
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
- 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.