Triple
T35552568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arakwal Indigenous Land Use Agreement area |
E1027402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | co-managed conservation area |
C40034
|
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: co-managed conservation area Context triple: [Arakwal Indigenous Land Use Agreement area, instanceOf, co-managed conservation area]
-
A.
co-managed protected area
chosen
A co-managed protected area is a conservation zone where responsibility and authority for managing natural resources and biodiversity are shared between government agencies and local communities or other stakeholders through formal agreements.
-
B.
wildlife management area
A wildlife management area is a designated tract of land or water managed primarily for the conservation, habitat protection, and regulated use of wildlife and natural resources.
-
C.
network of protected areas
A network of protected areas is a coordinated system of geographically distinct conservation sites managed collectively to maintain biodiversity, ecological processes, and landscape connectivity.
-
D.
protected area management body
A protected area management body is an organization or authority responsible for planning, regulating, and overseeing the conservation, use, and monitoring of a designated protected area and its natural and cultural resources.
-
E.
privately managed park
A privately managed park is a recreational green space owned or operated by a non-governmental entity that controls access, maintenance, and permitted activities, often funded through fees, memberships, or private investment.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.