Triple
T30073151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinburn Spit Regional Landscape Park |
E764241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional landscape park |
C22989
|
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: regional landscape park Context triple: [Kinburn Spit Regional Landscape Park, instanceOf, regional landscape park]
-
A.
parkland landscape
A parkland landscape is a designed or natural area characterized by open grassy spaces interspersed with groups of trees, paths, and recreational features, often intended for public enjoyment and ecological value.
-
B.
protected landscape area
chosen
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.
-
C.
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.
-
D.
scenic district
A scenic district is a designated geographic area recognized and protected for its outstanding natural beauty, cultural landscapes, and visual character, often managed to preserve its aesthetic and environmental qualities.
-
E.
rural park
A rural park is a natural or semi-natural public space located in the countryside, offering recreational opportunities and conservation of local landscapes and wildlife.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:01 p.m.