Triple
T18108584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Olav Ways |
E433412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pilgrimage route network |
C33795
|
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: pilgrimage route network Context triple: [St. Olav Ways, instanceOf, pilgrimage route network]
-
A.
pilgrimage network
chosen
A pilgrimage network is an interconnected system of sacred sites, routes, institutions, and supporting services that collectively structure and facilitate the movement and experiences of pilgrims.
-
B.
cultural heritage route
A cultural heritage route is a planned path or itinerary that connects sites, landscapes, and traditions of historical, artistic, or social significance to showcase and preserve a community’s or region’s cultural legacy.
-
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.
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.
-
E.
pilgrimage infrastructure project
A pilgrimage infrastructure project is a coordinated initiative to design, build, or upgrade facilities, routes, and services that support and enhance the experience, safety, and accessibility of religious or spiritual journeys.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:28 a.m.