Triple

T6310435
Position Surface form Disambiguated ID Type / Status
Subject Rotterdam–Antwerp inland waterway route E141486 entity
Predicate instanceOf P0 FINISHED
Object European 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: European transport corridor
Context triple: [Rotterdam–Antwerp inland waterway route, instanceOf, European transport corridor]
  • A. 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.
  • B. European transport agreement
    A European transport agreement is a formal, often multilateral, accord between European states that harmonizes rules, standards, and procedures for cross-border transportation of goods and passengers to ensure safety, efficiency, and legal consistency.
  • 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 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.
  • E. 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.
  • 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.