Triple
T35343627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Database of Key Biodiversity Areas |
E1020676
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | global environmental 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: global environmental database Context triple: [World Database of Key Biodiversity Areas, instanceOf, global environmental database]
-
A.
global environmental data centre
A global environmental data centre is an organization that collects, curates, archives, and distributes worldwide environmental and climate data to support research, policy-making, and public information.
-
B.
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.
-
C.
geoscience database
A geoscience database is a structured repository that stores, organizes, and enables retrieval and analysis of spatial, geological, geophysical, and geochemical data about the Earth.
-
D.
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.
-
E.
environmental knowledge network
An environmental knowledge network is a connected system of people, organizations, data, and tools that collaboratively collect, share, and apply information about the environment to support understanding, decision-making, and action.
- 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.