Triple

T13530968
Position Surface form Disambiguated ID Type / Status
Subject Arnhem–Nijmegen railway E323129 entity
Predicate owner P347 FINISHED
Object ProRail E74236 NE FINISHED

How this triple was built (2 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: ProRail | Statement: [Arnhem–Nijmegen railway, owner, ProRail]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ProRail
Context triple: [Arnhem–Nijmegen railway, owner, ProRail]
  • A. ProRail chosen
    ProRail is the Dutch government-owned company responsible for managing and maintaining the national railway infrastructure in the Netherlands.
  • B. Nederlandse Spoorwegen
    Nederlandse Spoorwegen is the principal Dutch railway company responsible for most passenger train services across the Netherlands.
  • C. Staatsspoorwegen
    Staatsspoorwegen was the main state-owned railway company of the Dutch East Indies, responsible for developing and operating much of the colonial-era rail infrastructure in what is now Indonesia.
  • D. SNCB/NMBS
    SNCB/NMBS is the Belgian national railway company responsible for operating most passenger train services and managing much of the rail infrastructure in Belgium.
  • E. Spoornet
    Spoornet was South Africa’s former state-owned freight rail operator, responsible for much of the country’s heavy rail transport before being restructured and rebranded.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d80766a21881909f21a1b7421d3b8a completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafba2c308190873efd15dfe26358 completed April 12, 2026, 2:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69f78adaf62c8190855df932eb9830be completed May 3, 2026, 5:50 p.m.
Created at: April 9, 2026, 9:44 p.m.