Triple
T7940057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Biodiversity Information Facility |
E184366
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biodiversity data infrastructure |
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: biodiversity data infrastructure Context triple: [Global Biodiversity Information Facility, instanceOf, biodiversity data infrastructure]
-
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.
biodiversity assessment
Biodiversity assessment is the systematic evaluation and measurement of the variety, abundance, and distribution of species, genes, and ecosystems within a defined area to understand ecological health and inform conservation decisions.
-
C.
biodiversity monitoring site
A biodiversity monitoring site is a designated location where systematic, repeated observations and measurements of species, habitats, and environmental conditions are conducted to track changes in biological diversity over time.
-
D.
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.
-
E.
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.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:08 p.m.