Triple
T8459739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Afromontane biodiversity hotspot |
E200010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conservation priority area |
C4853
|
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 priority area Context triple: [Eastern Afromontane biodiversity hotspot, instanceOf, conservation priority 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.
biodiversity hotspot
chosen
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.
Special Area of Conservation
A Special Area of Conservation is a protected site designated under the EU Habitats Directive to safeguard rare, endangered, or vulnerable natural habitats and species of European importance.
-
D.
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.
-
E.
protected area designation in the United States
A protected area designation in the United States is an official legal or administrative status applied to lands and waters to conserve natural, cultural, or recreational resources by regulating their use and development.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:10 p.m.