Triple

T16453772
Position Surface form Disambiguated ID Type / Status
Subject Randstad regional rail network E399619 entity
Predicate relatedInfrastructure P43089 FINISHED
Object Schiphol–Amsterdam–Almere–Lelystad corridor
The Schiphol–Amsterdam–Almere–Lelystad corridor is a major Dutch rail and transport axis connecting Amsterdam’s airport and eastern satellite cities within the Randstad metropolitan region.
E1215042 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: Schiphol–Amsterdam–Almere–Lelystad corridor | Statement: [Randstad regional rail network, relatedInfrastructure, Schiphol–Amsterdam–Almere–Lelystad corridor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schiphol–Amsterdam–Almere–Lelystad corridor
Context triple: [Randstad regional rail network, relatedInfrastructure, Schiphol–Amsterdam–Almere–Lelystad corridor]
  • A. Amsterdam–The Hague–Rotterdam corridor
    The Amsterdam–The Hague–Rotterdam corridor is a heavily trafficked rail and urban region in the western Netherlands that links the country’s largest Randstad cities through a continuous band of transportation and development.
  • 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. 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.
  • D. 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.
  • E. 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.
  • 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: Schiphol–Amsterdam–Almere–Lelystad corridor
Triple: [Randstad regional rail network, relatedInfrastructure, Schiphol–Amsterdam–Almere–Lelystad corridor]
Generated description
The Schiphol–Amsterdam–Almere–Lelystad corridor is a major Dutch rail and transport axis connecting Amsterdam’s airport and eastern satellite cities within the Randstad metropolitan region.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Schiphol–Amsterdam–Almere–Lelystad corridor
Target entity description: The Schiphol–Amsterdam–Almere–Lelystad corridor is a major Dutch rail and transport axis connecting Amsterdam’s airport and eastern satellite cities within the Randstad metropolitan region.
  • A. Amsterdam–The Hague–Rotterdam corridor
    The Amsterdam–The Hague–Rotterdam corridor is a heavily trafficked rail and urban region in the western Netherlands that links the country’s largest Randstad cities through a continuous band of transportation and development.
  • 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. 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.
  • D. 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.
  • E. 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.
  • 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_69d87f2c6778819080fcfae53be8f12a completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32ce259d88190803930051409d72c completed April 18, 2026, 7:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f4e31a08190b121d0cfe2a406c2 completed May 10, 2026, 9:26 a.m.
NEDg Description generation batch_6a00513b6fcc8190a548b30cb7b4b67f completed May 10, 2026, 9:34 a.m.
NED2 Entity disambiguation (via description) batch_6a0051def1d48190b40f55c40ab269d2 completed May 10, 2026, 9:37 a.m.
Created at: April 10, 2026, 5:10 a.m.