Triple
T21641693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetepare Island conservation area |
E534102
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community-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: community-managed conservation area Context triple: [Tetepare Island conservation area, instanceOf, community-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.
conservation district
A conservation district is a designated geographic area where natural resources are managed and protected through coordinated planning, regulation, and community-based conservation practices.
-
D.
Conservation area
A conservation area is a designated geographic region managed to protect and preserve its natural, cultural, or historical resources and biodiversity from degradation or unsustainable use.
-
E.
protected natural area system
A protected natural area system is an organized network of geographically defined spaces managed through legal or other effective means to conserve biodiversity, ecosystem services, and natural or cultural values over the long term.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:35 p.m.