Triple
T12186028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Database on Protected Areas |
E290336
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conservation information system |
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 information system Context triple: [World Database on Protected Areas, instanceOf, conservation information system]
-
A.
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.
-
B.
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.
-
C.
conservation status
Conservation status is a classification that indicates the likelihood that a species or ecosystem will remain extant in the near future, based on factors such as population trends, threats, and habitat conditions.
-
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.
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.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:50 p.m.