Triple
T13019111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Key Biodiversity Area |
E322629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conservation site classification |
C22935
|
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 site classification Context triple: [Key Biodiversity Area, instanceOf, conservation site classification]
-
A.
Special Area of Conservation
A Special Area of Conservation is a protected site designated under the EU Habitats Directive to safeguard rare, endangered, or vulnerable natural habitats and species of European importance.
-
B.
landscape conservation category
A landscape conservation category is a classification used to designate and manage areas where the primary goal is to protect and sustain the ecological, cultural, and scenic values of large-scale natural or semi-natural landscapes.
-
C.
Protected area designation
chosen
A protected area designation is an official classification assigned to a geographic region to conserve its natural, cultural, or ecological values by regulating human activities and land use.
-
D.
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.
-
E.
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.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:51 p.m.