Triple

T6368359
Position Surface form Disambiguated ID Type / Status
Subject municipality of Spijkenisse E143283 entity
Predicate locatedOnTransportCorridor P2409 FINISHED
Object Rotterdam–Hellevoetsluis corridor
The Rotterdam–Hellevoetsluis corridor is a key regional transport axis in South Holland, connecting the port city of Rotterdam with the town of Hellevoetsluis and serving several intermediate municipalities.
E589122 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–Hellevoetsluis corridor | Statement: [municipality of Spijkenisse, locatedOnTransportCorridor, Rotterdam–Hellevoetsluis corridor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rotterdam–Hellevoetsluis corridor
Context triple: [municipality of Spijkenisse, locatedOnTransportCorridor, Rotterdam–Hellevoetsluis corridor]
  • A. Leiden–Alphen–Utrecht corridor
    The Leiden–Alphen–Utrecht corridor is a Dutch railway line connecting the cities of Leiden, Alphen aan den Rijn, and Utrecht as part of the Randstad region’s regional rail network.
  • B. 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.
  • C. A2 Amsterdam–Maastricht corridor
    The A2 Amsterdam–Maastricht corridor is a major north–south Dutch motorway route connecting the capital Amsterdam with the southern city of Maastricht and forming a key part of the Netherlands’ primary road network.
  • D. Nijmegen–Maastricht transport corridor
    The Nijmegen–Maastricht transport corridor is a major north–south route in the Netherlands that links the cities of Nijmegen and Maastricht via an integrated network of motorways and other transport infrastructure.
  • E. Eindhoven–Nijmegen–Arnhem corridor
    The Eindhoven–Nijmegen–Arnhem corridor is a strategically important region in the southern and eastern Netherlands, encompassing a chain of cities and river crossings that has served as a key transportation and military axis.
  • 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–Hellevoetsluis corridor
Triple: [municipality of Spijkenisse, locatedOnTransportCorridor, Rotterdam–Hellevoetsluis corridor]
Generated description
The Rotterdam–Hellevoetsluis corridor is a key regional transport axis in South Holland, connecting the port city of Rotterdam with the town of Hellevoetsluis and serving several intermediate municipalities.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Rotterdam–Hellevoetsluis corridor
Target entity description: The Rotterdam–Hellevoetsluis corridor is a key regional transport axis in South Holland, connecting the port city of Rotterdam with the town of Hellevoetsluis and serving several intermediate municipalities.
  • A. Leiden–Alphen–Utrecht corridor
    The Leiden–Alphen–Utrecht corridor is a Dutch railway line connecting the cities of Leiden, Alphen aan den Rijn, and Utrecht as part of the Randstad region’s regional rail network.
  • B. 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.
  • C. A2 Amsterdam–Maastricht corridor
    The A2 Amsterdam–Maastricht corridor is a major north–south Dutch motorway route connecting the capital Amsterdam with the southern city of Maastricht and forming a key part of the Netherlands’ primary road network.
  • D. Nijmegen–Maastricht transport corridor
    The Nijmegen–Maastricht transport corridor is a major north–south route in the Netherlands that links the cities of Nijmegen and Maastricht via an integrated network of motorways and other transport infrastructure.
  • E. Eindhoven–Nijmegen–Arnhem corridor
    The Eindhoven–Nijmegen–Arnhem corridor is a strategically important region in the southern and eastern Netherlands, encompassing a chain of cities and river crossings that has served as a key transportation and military axis.
  • 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_69c008d8c61081908bcaf61510d881ed completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c068251ae48190af8201d5f9ad35b6 completed March 22, 2026, 10:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c62d8689408190b334928df870ed29 completed March 27, 2026, 7:11 a.m.
NEDg Description generation batch_69c6312d8a2c8190ad916969b0331170 completed March 27, 2026, 7:26 a.m.
NED2 Entity disambiguation (via description) batch_69c63185bf28819096e518e23362a701 completed March 27, 2026, 7:28 a.m.
Created at: March 22, 2026, 4:32 p.m.