Triple
T26350923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torra Conservancy |
E662898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community-based natural resource management 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-based natural resource management area Context triple: [Torra Conservancy, instanceOf, community-based natural resource management 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.
ecosystem management unit
An ecosystem management unit is a defined geographic or ecological area managed as a coherent whole to maintain or restore its biodiversity, ecological processes, and sustainable resource use.
-
D.
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.
-
E.
wilderness study area
A wilderness study area is a region of public land identified and managed for its natural, undeveloped character while being evaluated for potential permanent wilderness designation.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:45 p.m.