Triple

T19531081
Position Surface form Disambiguated ID Type / Status
Subject High-Speed Line South E488652 entity
Predicate hasSection P35 FINISHED
Object Rotterdam–Breda high-speed section — NE NERFINISHED

How this triple was built (3 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–Breda high-speed section | Statement: [High-Speed Line South, hasSection, Rotterdam–Breda high-speed section]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Rotterdam–Breda high-speed section
Context triple: [High-Speed Line South, hasSection, Rotterdam–Breda high-speed section]
  • A. Schiphol–Rotterdam high-speed section
    The Schiphol–Rotterdam high-speed section is a Dutch railway line segment designed for high-speed passenger trains, connecting Amsterdam Airport Schiphol with Rotterdam as part of the country’s main high-speed rail corridor.
  • B. Amsterdam–Eindhoven railway corridor
    The Amsterdam–Eindhoven railway corridor is a major Dutch rail axis connecting the capital Amsterdam with the southern city of Eindhoven, serving as a key route for both intercity and regional train services.
  • C. Amsterdam–Utrecht railway
    The Amsterdam–Utrecht railway is a major Dutch mainline rail route connecting Amsterdam with Utrecht and forming part of a key north–south transport corridor in the Netherlands.
  • D. Eindhoven–Maastricht railway
    The Eindhoven–Maastricht railway is a major rail line in the Netherlands connecting the city of Eindhoven with Maastricht and serving several intermediate towns in the Limburg region.
  • E. Tilburg–Nijmegen railway
    The Tilburg–Nijmegen railway is a Dutch rail line in the southern Netherlands that connects the cities of Tilburg and Nijmegen via intermediate towns such as Oss.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Rotterdam–Breda high-speed section
Target entity description: The Rotterdam–Breda high-speed section is a Dutch railway corridor designed for high-speed passenger services, linking the major cities of Rotterdam and Breda as part of the national high-speed rail network.
  • A. Schiphol–Rotterdam high-speed section
    The Schiphol–Rotterdam high-speed section is a Dutch railway line segment designed for high-speed passenger trains, connecting Amsterdam Airport Schiphol with Rotterdam as part of the country’s main high-speed rail corridor.
  • B. Amsterdam–Eindhoven railway corridor
    The Amsterdam–Eindhoven railway corridor is a major Dutch rail axis connecting the capital Amsterdam with the southern city of Eindhoven, serving as a key route for both intercity and regional train services.
  • C. Amsterdam–Utrecht railway
    The Amsterdam–Utrecht railway is a major Dutch mainline rail route connecting Amsterdam with Utrecht and forming part of a key north–south transport corridor in the Netherlands.
  • D. Eindhoven–Maastricht railway
    The Eindhoven–Maastricht railway is a major rail line in the Netherlands connecting the city of Eindhoven with Maastricht and serving several intermediate towns in the Limburg region.
  • E. Tilburg–Nijmegen railway
    The Tilburg–Nijmegen railway is a Dutch rail line in the southern Netherlands that connects the cities of Tilburg and Nijmegen via intermediate towns such as Oss.
  • F. None of above. chosen

Provenance (2 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_69d8e8db5b6c8190984b61f91981f575 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6363ec6cc8190b9e9ac0196b288f9 completed April 20, 2026, 2:20 p.m.
Created at: April 10, 2026, 1:41 p.m.