Triple

T14974719
Position Surface form Disambiguated ID Type / Status
Subject Belgian railway line 36 E373414 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: [Belgian railway line 36, operator, SNCB/NMBS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SNCB/NMBS
Context triple: [Belgian railway line 36, 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. Belgian InterCity network
    The Belgian InterCity network is a system of fast, long-distance passenger train services connecting major cities and regional hubs across Belgium.
  • D. Intercity Brussels
    Intercity Brussels is an international high-speed train service connecting the Netherlands with Brussels in Belgium.
  • E. ProRail
    ProRail is the Dutch government-owned company responsible for managing and maintaining the national railway infrastructure in the Netherlands.
  • 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_69d85ccbbcd48190acb56e7cf104d8ad completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded6e8733081908e06b53746eb6eb6 completed April 15, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe8beac05c8190bf19ec8bd1eab2d8 completed May 9, 2026, 1:20 a.m.
Created at: April 10, 2026, 2:51 a.m.