Triple
T19925290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E4 European long-distance path |
E478906
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European long-distance path |
C3572
|
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: European long-distance path Context triple: [E4 European long-distance path, instanceOf, European long-distance path]
-
A.
long-distance footpath
chosen
A long-distance footpath is an extended, often waymarked walking route designed for multi-day journeys across varied landscapes, typically connecting towns, natural landmarks, or regions.
-
B.
long-distance cycle route
A long-distance cycle route is a designated, often waymarked cycling corridor that spans substantial distances, connecting regions or countries and providing cyclists with a continuous, safe, and scenic path for multi-day journeys.
-
C.
Camino de Santiago route
A Camino de Santiago route is a historically rooted pilgrimage path, composed of interconnected waypoints, infrastructure, and cultural landmarks, that guides travelers from various starting points to the shrine of Saint James in Santiago de Compostela.
-
D.
Grande Randonnée route
A Grande Randonnée route is a long-distance, waymarked hiking trail, primarily found in Europe, designed for multi-day treks through varied natural and cultural landscapes.
-
E.
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.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:53 p.m.