Triple

T7130202
Position Surface form Disambiguated ID Type / Status
Subject Brussels-South railway station E166166 entity
Predicate ownedBy P347 FINISHED
Object SNCB 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 | Statement: [Brussels-South railway station, ownedBy, SNCB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SNCB
Context triple: [Brussels-South railway station, ownedBy, SNCB]
  • 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_69c6888350588190870cd552b427a1cd completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e66dc2388190bdec018f1cc6b20a completed March 27, 2026, 8:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7a33eea0481909f87e0813bc35b52 completed March 28, 2026, 9:45 a.m.
Created at: March 27, 2026, 2:44 p.m.