Triple
T28119616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels–Luxembourg rail corridor |
E710741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international railway corridor |
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: international railway corridor Context triple: [Brussels–Luxembourg rail corridor, instanceOf, international railway corridor]
-
A.
international railway
An international railway is a rail transport system or route that connects and facilitates the movement of passengers and freight between two or more countries across their national borders.
-
B.
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.
-
C.
international road
An international road is a major transportation route that connects multiple countries, facilitating cross-border travel and trade by linking national road networks.
-
D.
international transport project
An international transport project is a coordinated initiative that plans, finances, and implements cross-border transportation infrastructure or services to improve connectivity, efficiency, and economic integration between countries.
-
E.
freight rail corridor
A freight rail corridor is a designated railway route primarily used for the efficient, high-capacity movement of goods and cargo between industrial, commercial, and logistics hubs.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 9:16 p.m.