Triple

T21288149
Position Surface form Disambiguated ID Type / Status
Subject Solothurn–Langnau railway line E524715 entity
Predicate operator P179 FINISHED
Object BLS AG NE NERFINISHED

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: BLS AG | Statement: [Solothurn–Langnau railway line, operator, BLS AG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BLS AG
Context triple: [Solothurn–Langnau railway line, operator, BLS AG]
  • A. BLS AG chosen
    BLS AG is a major Swiss railway company that operates regional and commuter train services, particularly in and around the canton of Bern.
  • B. Brugg AG
    Brugg AG is a municipality in the canton of Aargau in northern Switzerland, known as a regional transport hub and local economic center.
  • C. Schenker AG
    Schenker AG is a global logistics and freight forwarding company headquartered in Germany and operating under the DB Schenker brand.
  • D. BLS Schifffahrt
    BLS Schifffahrt is a Swiss shipping company that operates passenger boat services on lakes in the Bernese Oberland region.
  • E. Aral AG
    Aral AG is a major German brand of fuel stations and petroleum products, widely recognized for its network of service stations across Germany.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5171f6c8190a5d57201ede73811 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e736d7c57c8190bc4180ea590a62d4 completed April 21, 2026, 8:35 a.m.
Created at: April 16, 2026, 4:03 p.m.