Triple
T35343626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Database of Key Biodiversity Areas |
E1020676
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conservation database |
C2226
|
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 database Context triple: [World Database of Key Biodiversity Areas, instanceOf, conservation database]
-
A.
biodiversity database
chosen
A biodiversity database is a structured digital repository that stores, organizes, and provides access to data on species, their distributions, traits, and ecological relationships to support research, conservation, and environmental management.
-
B.
protected areas database
A protected areas database is a structured repository that stores, organizes, and provides access to information about designated conservation sites, including their locations, legal status, management, and ecological characteristics.
-
C.
site-based conservation tool
A site-based conservation tool is a system or application designed to assess, prioritize, and manage conservation actions at specific geographic locations to protect biodiversity and ecosystem services.
-
D.
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.
-
E.
environmental database
An environmental database is a structured collection of data related to natural resources, ecosystems, pollution, climate, and other environmental factors, designed to support analysis, monitoring, and decision-making.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.