Triple
T13771302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcastle coastal walk network |
E330886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coastal walking trail 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: coastal walking trail network Context triple: [Newcastle coastal walk network, instanceOf, coastal walking trail network]
-
A.
long-distance hiking trail network
A long-distance hiking trail network is an interconnected system of marked footpaths spanning large geographic areas, designed to support extended, multi-day trekking experiences between various natural and cultural destinations.
-
B.
recreation trail
A recreation trail is a designated path or route intended for non-motorized leisure activities such as walking, hiking, cycling, or horseback riding, often located in natural or scenic areas.
-
C.
waterfront greenway
A waterfront greenway is a linear, publicly accessible open space along a body of water that combines pedestrian and bicycle paths with landscaping, recreation areas, and ecological features to connect communities and enhance shoreline environments.
-
D.
rail trail
A rail trail is a multi-use path created from a disused railway corridor, typically used for walking, cycling, and other non-motorized recreation and transportation.
-
E.
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.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:10 p.m.