Triple
T34182159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camino Finisterre-Muxía |
E876849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | extension of the Camino de Santiago |
C34250
|
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: extension of the Camino de Santiago Context triple: [Camino Finisterre-Muxía, instanceOf, extension of the Camino de Santiago]
-
A.
Camino de Santiago route
chosen
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.
-
B.
road in Spain
A road in Spain is a public thoroughfare within Spanish territory, ranging from local streets to national highways, designed for vehicular and pedestrian transit under Spain’s traffic and infrastructure regulations.
-
C.
Chilean road
A Chilean road is a transportation route within Chile’s national or regional network, designed for vehicular travel and identified by a specific classification and numbering system.
-
D.
Spanish national road
A Spanish national road is a major public roadway within Spain’s national highway network that connects key cities and regions, facilitating long-distance vehicular travel and transport.
-
E.
bridge in Spain
A bridge in Spain is a structural construction that spans physical obstacles such as rivers, valleys, or roads within Spanish territory, facilitating transportation and connectivity while often reflecting the country’s diverse historical and architectural styles.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:55 a.m.