Triple
T2796248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IUCN Red List Categories and Criteria |
E53043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biodiversity risk classification system |
C8063
|
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 risk classification system Context triple: [IUCN Red List Categories and Criteria, instanceOf, biodiversity risk classification system]
-
A.
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.
-
B.
biodiversity database
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.
-
C.
conservation status
chosen
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 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.
ecosystem
An ecosystem is a dynamic community of living organisms interacting with each other and with their physical environment as a functional unit.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:58 p.m.