Triple

T8601688
Position Surface form Disambiguated ID Type / Status
Subject Brussels–Amsterdam E203690 entity
Predicate operator P179 FINISHED
Object SNCB-NMBS E78978 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: SNCB-NMBS | Statement: [Brussels–Amsterdam, operator, SNCB-NMBS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SNCB-NMBS
Context triple: [Brussels–Amsterdam, operator, SNCB-NMBS]
  • A. SNCB/NMBS chosen
    SNCB/NMBS is the Belgian national railway company responsible for operating most passenger train services and managing much of the rail infrastructure in Belgium.
  • B. Infrabel
    Infrabel is the Belgian railway infrastructure manager responsible for the construction, maintenance, and operation of the national rail network.
  • C. Intercity Brussels
    Intercity Brussels is an international high-speed train service connecting the Netherlands with Brussels in Belgium.
  • D. ProRail
    ProRail is the Dutch government-owned company responsible for managing and maintaining the national railway infrastructure in the Netherlands.
  • E. STIB-MIVB
    STIB-MIVB is the primary public transport company in Brussels, Belgium, operating the city’s metro, tram, and bus networks.
  • 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_69ca832b56948190ba751cec255308f1 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc46da609881909a6d851915e8df14 completed March 31, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69cea8f13f7081908317c1b2d87a51b2 completed April 2, 2026, 5:35 p.m.
Created at: March 30, 2026, 6:24 p.m.