Triple
T14770369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunnel of Trees Scenic Heritage Route |
E347114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage route |
C19666
|
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: heritage route Context triple: [Tunnel of Trees Scenic Heritage Route, instanceOf, heritage route]
-
A.
cultural heritage route
chosen
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.
-
B.
National Tourist Route
A National Tourist Route is a designated roadway or travel corridor recognized for its exceptional scenic, cultural, and recreational value, developed and managed to enhance visitor experiences and promote regional tourism.
-
C.
historic road
A historic road is a transportation route of significant age and cultural, economic, or political importance, preserved or recognized for its role in shaping historical events, trade, or settlement patterns.
-
D.
ancient route listing
An ancient route listing is a documented catalog of historical travel paths, roads, or trade routes, often detailing their locations, connections, and significance in past civilizations.
-
E.
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.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.