Triple
T35140185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alliance for Zero Extinction site |
E1014683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biodiversity conservation priority area |
C57624
|
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: biodiversity conservation priority area Context triple: [Alliance for Zero Extinction site, instanceOf, biodiversity conservation priority area]
-
A.
Key Biodiversity Area
chosen
A Key Biodiversity Area is a geographically defined site that significantly contributes to the global persistence of biodiversity, identified using standardized, science-based criteria.
-
B.
biodiversity hotspot
A biodiversity hotspot is a biogeographic region with exceptionally high levels of species richness and endemism that is under significant threat from human activities.
-
C.
biodiversity conservation initiative
A biodiversity conservation initiative is a coordinated effort or program designed to protect, restore, and sustainably manage the variety of life in ecosystems, species, and genetic resources within a defined area or context.
-
D.
area-based conservation measure
An area-based conservation measure is a geographically defined space managed through legal or other effective means to achieve long-term conservation of nature and associated ecosystem services and cultural values.
-
E.
Protected area designation
A protected area designation is an official classification assigned to a geographic region to conserve its natural, cultural, or ecological values by regulating human activities and land use.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.