Triple

T28645662
Position Surface form Disambiguated ID Type / Status
Subject west–east European inland waterway corridor E725047 entity
Predicate instanceOf P0 FINISHED
Object trans-European transport network component C49884 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: trans-European transport network component
Context triple: [west–east European inland waterway corridor, instanceOf, trans-European transport network component]
  • A. trans-European transport network route chosen
    A trans-European transport network route is a designated corridor within the EU-wide integrated transport system that connects key cities, ports, and regions across Europe to facilitate efficient, interoperable, and sustainable cross-border movement of people and goods.
  • B. trans-European road
    A trans-European road is a major transportation route that crosses multiple European countries, facilitating international travel and trade across the continent.
  • 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. Polish expressway
    A Polish expressway is a high-capacity, limited-access road in Poland designed for fast regional and intercity traffic, typically featuring dual carriageways, grade-separated junctions, and controlled entry and exit points.
  • E. 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.
  • 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_69f01d8423888190bd2f4e52605bf261 completed April 28, 2026, 2:37 a.m.
Created at: April 28, 2026, 4:47 a.m.