Triple
T32120285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peak District National Park rights of way network |
E820351
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rights of way network |
C15867
|
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: rights of way network Context triple: [Peak District National Park rights of way network, instanceOf, rights of way network]
-
A.
road network
A road network is an interconnected system of roads, intersections, and related infrastructure that enables the movement of vehicles and pedestrians between different locations.
-
B.
trail system
chosen
A trail system is an interconnected network of designated paths and routes designed to guide users through natural or built environments for recreation, transportation, or exploration.
-
C.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
D.
pedestrian network
A pedestrian network is an interconnected system of walkways, sidewalks, crossings, and paths designed to facilitate safe and efficient movement of people on foot within and between areas.
-
E.
tourist route network
A tourist route network is an interconnected system of paths, attractions, and services designed to guide visitors efficiently and enjoyably through a region’s key points of interest.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:28 a.m.