Triple
T33759861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European long-distance hiking routes network |
E865077
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transnational hiking trail system |
C26226
|
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: transnational hiking trail system Context triple: [European long-distance hiking routes network, instanceOf, transnational hiking trail system]
-
A.
long-distance hiking trail network
chosen
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.
long-distance hiking trail
A long-distance hiking trail is an extended, often multi-day walking route designed for recreational trekking through diverse natural landscapes, typically marked and maintained for continuous foot travel.
-
C.
trail system
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.
-
D.
backcountry hiking trail
A backcountry hiking trail is a remote, minimally developed path through natural landscapes that offers challenging terrain, limited amenities, and opportunities for solitude and wilderness exploration.
-
E.
Indigenous travel corridor
An Indigenous travel corridor is a traditional route or network of pathways used by Indigenous peoples for movement, trade, cultural exchange, and connection across their ancestral lands.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.