Triple
T6310434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotterdam–Antwerp inland waterway route |
E141486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | freight transport 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: freight transport corridor Context triple: [Rotterdam–Antwerp inland waterway route, instanceOf, freight transport corridor]
-
A.
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.
-
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.
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.
-
D.
freight transport sector
The freight transport sector encompasses the systems, services, and infrastructure involved in moving goods by road, rail, sea, air, and inland waterways across local, regional, and global supply chains.
-
E.
transportation corridors collection
A transportation corridors collection is an organized set of linear pathways—such as roads, railways, and transit routes—grouped for managing, analyzing, or planning movement across a region.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:28 p.m.