Triple
T27171232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Alps transport network |
E682914
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transalpine transport system |
C2952
|
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: transalpine transport system Context triple: [Western Alps transport network, instanceOf, transalpine transport system]
-
A.
transalpine railway
A transalpine railway is a rail line that crosses or traverses the Alps, typically using tunnels, viaducts, and mountain passes to connect regions on either side of the mountain range.
-
B.
transalpine trade route
A transalpine trade route is a transportation corridor that crosses the Alps to facilitate the movement of goods, people, and cultural exchange between regions on either side of the mountain range.
-
C.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
D.
transport corridor
chosen
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
E.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:23 a.m.