Triple

T21328794
Position Surface form Disambiguated ID Type / Status
Subject A9 motorway E525838 entity
Predicate partOfCorridor P840 FINISHED
Object Amsterdam–Alkmaar corridor — 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: Amsterdam–Alkmaar corridor | Statement: [A9 motorway, partOfCorridor, Amsterdam–Alkmaar corridor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Amsterdam–Alkmaar corridor
Context triple: [A9 motorway, partOfCorridor, Amsterdam–Alkmaar corridor]
  • A. Rotterdam–The Hague corridor
    The Rotterdam–The Hague corridor is a major urban and transport axis in the western Netherlands that links the cities of Rotterdam and The Hague within the densely populated Randstad metropolitan region.
  • B. Amsterdam-Utrecht corridor
    The Amsterdam-Utrecht corridor is a major urban and transportation axis in the Netherlands linking the cities of Amsterdam and Utrecht and encompassing several intermediate municipalities and economic hubs.
  • C. Nijmegen–Oss corridor
    The Nijmegen–Oss corridor is a key Dutch transport axis linking the cities of Nijmegen and Oss and serving intermediate municipalities such as Wijchen.
  • D. Haarlem–Leiden corridor
    The Haarlem–Leiden corridor is a key transport axis in the western Netherlands linking the cities of Haarlem and Leiden through a network of roads and other infrastructure.
  • E. 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.
  • 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: Amsterdam–Alkmaar corridor
Target entity description: The Amsterdam–Alkmaar corridor is a major transport axis in the Netherlands linking the Amsterdam metropolitan area with the city of Alkmaar through a network of roads and other infrastructure.
  • A. Rotterdam–The Hague corridor
    The Rotterdam–The Hague corridor is a major urban and transport axis in the western Netherlands that links the cities of Rotterdam and The Hague within the densely populated Randstad metropolitan region.
  • B. Amsterdam-Utrecht corridor
    The Amsterdam-Utrecht corridor is a major urban and transportation axis in the Netherlands linking the cities of Amsterdam and Utrecht and encompassing several intermediate municipalities and economic hubs.
  • C. Nijmegen–Oss corridor
    The Nijmegen–Oss corridor is a key Dutch transport axis linking the cities of Nijmegen and Oss and serving intermediate municipalities such as Wijchen.
  • D. Haarlem–Leiden corridor
    The Haarlem–Leiden corridor is a key transport axis in the western Netherlands linking the cities of Haarlem and Leiden through a network of roads and other infrastructure.
  • E. 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.
  • 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_69e0b51b90788190a4dd823d962626da completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7ab4f95fc819087eb32dca7da689a completed April 21, 2026, 4:52 p.m.
Created at: April 16, 2026, 4:42 p.m.