Triple

T960182
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam Sloterdijk E20717 entity
Predicate operatedBy P86 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: [Amsterdam Sloterdijk, operatedBy, ProRail]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ProRail
Context triple: [Amsterdam Sloterdijk, operatedBy, 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. 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.
  • E. Deutsche Bahn
    Deutsche Bahn is Germany's state-owned national railway company and one of the largest rail and logistics operators in Europe.
  • 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_69a493b21f2881908132dcf45dcd2f36 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b412f9f48190be123e8c20f38962 completed March 1, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac2a11e4148190bb18849c52c2ed9a completed March 7, 2026, 1:37 p.m.
Created at: March 1, 2026, 7:40 p.m.