Triple

T6945473
Position Surface form Disambiguated ID Type / Status
Subject Elbe–Havel Canal E160786 entity
Predicate partOfCorridor P840 FINISHED
Object Rotterdam–Berlin–Poland inland waterway route
The Rotterdam–Berlin–Poland inland waterway route is a major trans-European shipping corridor linking the North Sea port of Rotterdam with Berlin and onward to Poland via interconnected rivers and canals.
E631891 NE FINISHED

How this triple was built (4 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Rotterdam–Berlin–Poland inland waterway route | Statement: [Elbe–Havel Canal, partOfCorridor, Rotterdam–Berlin–Poland inland waterway route]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rotterdam–Berlin–Poland inland waterway route
Context triple: [Elbe–Havel Canal, partOfCorridor, Rotterdam–Berlin–Poland inland waterway route]
  • A. Rotterdam–Antwerp inland waterway route
    The Rotterdam–Antwerp inland waterway route is a major European shipping corridor connecting the ports of Rotterdam in the Netherlands and Antwerp in Belgium via rivers and canals used for intensive freight transport.
  • B. Amsterdam–IJsselmeer shipping route
    The Amsterdam–IJsselmeer shipping route is a key inland waterway in the Netherlands that connects the city of Amsterdam with the IJsselmeer lake, facilitating both commercial and recreational vessel traffic.
  • C. Meuse–Rhine Canal
    The Meuse–Rhine Canal is a major Dutch waterway that links the Meuse and Rhine river systems to facilitate inland shipping and transport.
  • D. Scheldt–Rhine Canal
    The Scheldt–Rhine Canal is a major shipping canal in the Netherlands that provides a direct navigable link between the Scheldt and Rhine river systems, facilitating international maritime and inland transport.
  • E. Rhine–Scheldt delta inland waterway network
    The Rhine–Scheldt delta inland waterway network is an interconnected system of navigable rivers and canals in the Rhine–Scheldt delta region that supports major European freight and transport routes between the North Sea ports and the continent’s interior.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Rotterdam–Berlin–Poland inland waterway route
Triple: [Elbe–Havel Canal, partOfCorridor, Rotterdam–Berlin–Poland inland waterway route]
Generated description
The Rotterdam–Berlin–Poland inland waterway route is a major trans-European shipping corridor linking the North Sea port of Rotterdam with Berlin and onward to Poland via interconnected rivers and canals.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Rotterdam–Berlin–Poland inland waterway route
Target entity description: The Rotterdam–Berlin–Poland inland waterway route is a major trans-European shipping corridor linking the North Sea port of Rotterdam with Berlin and onward to Poland via interconnected rivers and canals.
  • A. Rotterdam–Antwerp inland waterway route
    The Rotterdam–Antwerp inland waterway route is a major European shipping corridor connecting the ports of Rotterdam in the Netherlands and Antwerp in Belgium via rivers and canals used for intensive freight transport.
  • B. Amsterdam–IJsselmeer shipping route
    The Amsterdam–IJsselmeer shipping route is a key inland waterway in the Netherlands that connects the city of Amsterdam with the IJsselmeer lake, facilitating both commercial and recreational vessel traffic.
  • C. Meuse–Rhine Canal
    The Meuse–Rhine Canal is a major Dutch waterway that links the Meuse and Rhine river systems to facilitate inland shipping and transport.
  • D. Scheldt–Rhine Canal
    The Scheldt–Rhine Canal is a major shipping canal in the Netherlands that provides a direct navigable link between the Scheldt and Rhine river systems, facilitating international maritime and inland transport.
  • E. Rhine–Scheldt delta inland waterway network
    The Rhine–Scheldt delta inland waterway network is an interconnected system of navigable rivers and canals in the Rhine–Scheldt delta region that supports major European freight and transport routes between the North Sea ports and the continent’s interior.
  • F. None of above. chosen

Provenance (5 batches)

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_69c68850419081909fb426b8f5a304c7 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6da8a65c48190b6862fc60f6c7f7a completed March 27, 2026, 7:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7586b6f0c8190a6caad7d020e9c4d completed March 28, 2026, 4:26 a.m.
NEDg Description generation batch_69c75a417b7481908846a53712ea2323 completed March 28, 2026, 4:34 a.m.
NED2 Entity disambiguation (via description) batch_69c75abf8de881908e1ae0a46da795bc completed March 28, 2026, 4:36 a.m.
Created at: March 27, 2026, 2:28 p.m.