Triple
T32411363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conservation Partners Network |
E828229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conservation partnership network |
C10806
|
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: conservation partnership network Context triple: [Conservation Partners Network, instanceOf, conservation partnership network]
-
A.
environmental partnership
chosen
An environmental partnership is a collaborative relationship between organizations, communities, or stakeholders formed to jointly plan and implement actions that protect, restore, or sustainably manage natural resources and ecosystems.
-
B.
Conservation International program
A Conservation International program is an organized initiative that applies science, partnerships, and policy advocacy to protect nature and promote sustainable development in specific regions or thematic areas.
-
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.
conservation finance initiative
A conservation finance initiative is a structured program that mobilizes and manages capital to protect, restore, and sustainably use natural ecosystems while delivering measurable environmental and financial returns.
-
E.
conservation center
A conservation center is a facility dedicated to protecting, studying, and restoring wildlife, habitats, and natural resources through research, education, and hands-on management.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:53 a.m.