Triple

T8553915
Position Surface form Disambiguated ID Type / Status
Subject Haarlem–Leiden railway E202511 entity
Predicate hasOwner 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: [Haarlem–Leiden railway, hasOwner, ProRail]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ProRail
Context triple: [Haarlem–Leiden railway, hasOwner, 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. 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.
  • D. 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.
  • E. Amsterdam–Schiphol railway
    The Amsterdam–Schiphol railway is a key rail line in the Netherlands that connects central Amsterdam with Schiphol Airport and other major routes in the Randstad region.
  • 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_69ca832610e08190b3b6c6cd2c250255 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe8894e7c8190bc0ae2ceec473ecb completed March 31, 2026, 3:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce892efdf8819093c966bd8f6c8065 completed April 2, 2026, 3:20 p.m.
Created at: March 30, 2026, 6:19 p.m.