Triple
T12734976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veľká Fatra National Park |
E304338
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mountain range protected area |
C8950
|
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: mountain range protected area Context triple: [Veľká Fatra National Park, instanceOf, mountain range protected area]
-
A.
Andean mountain protected area
An Andean mountain protected area is a designated conservation region within the Andes that safeguards high-altitude ecosystems, endemic biodiversity, and cultural landscapes while regulating human activities to ensure long-term ecological integrity.
-
B.
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.
-
C.
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.
-
D.
mountain region
chosen
A mountain region is a large geographic area characterized by elevated terrain, significant relief, and distinct climatic and ecological conditions associated with mountainous landscapes.
-
E.
Protected natural area
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.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:26 p.m.