Triple
T24957510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Šumava |
E624515
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected natural region |
C26411
|
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: protected natural region Context triple: [Šumava, instanceOf, protected natural region]
-
A.
Protected natural area
chosen
A protected natural area is a geographically defined space designated and managed to conserve biodiversity, natural resources, and ecosystem services while limiting or regulating human activities.
-
B.
protected natural area system
A protected natural area system is an organized network of geographically defined spaces managed through legal or other effective means to conserve biodiversity, ecosystem services, and natural or cultural values over the long term.
-
C.
protected landscape area
A protected landscape area is a designated region where the interaction of people and nature over time has produced a distinct character with significant ecological, cultural, and scenic value that is conserved and managed through legal or other effective means.
-
D.
nature reserve
A nature reserve is a protected area of land or water designated to conserve wildlife, habitats, and natural features, often limiting human activities to research, education, and low-impact recreation.
-
E.
National Scenic Area
A National Scenic Area is a designated region recognized and protected for its outstanding natural beauty, distinctive landscapes, and cultural or recreational value, managed to conserve its character while allowing compatible public enjoyment and sustainable use.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 5:58 a.m.