Triple
T17901426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worimi Conservation Lands |
E447587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | co-managed protected 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 protected area Context triple: [Worimi Conservation Lands, instanceOf, co-managed protected area]
-
A.
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.
-
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.
protected area management plan
A protected area management plan is a strategic document that outlines objectives, policies, and actions for conserving biodiversity and managing human use within a designated protected area over a defined period.
-
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.
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. chosen
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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:19 a.m.