Triple

T18072302
Position Surface form Disambiguated ID Type / Status
Subject Bonn Stadtbahn lines E432459 entity
Predicate fareSystem P395 FINISHED
Object Verkehrsverbund Rhein-Sieg NE NERFINISHED

How this triple was built (3 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: Verkehrsverbund Rhein-Sieg | Statement: [Bonn Stadtbahn lines, fareSystem, Verkehrsverbund Rhein-Sieg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Verkehrsverbund Rhein-Sieg
Context triple: [Bonn Stadtbahn lines, fareSystem, Verkehrsverbund Rhein-Sieg]
  • A. Verkehrsverbund Rhein-Ruhr
    Verkehrsverbund Rhein-Ruhr is a major German public transport association that coordinates and integrates regional and local transit services across the Rhine-Ruhr metropolitan area in North Rhine-Westphalia.
  • B. Rhein-Main-Verkehrsverbund
    Rhein-Main-Verkehrsverbund is the regional public transport association that coordinates and manages integrated ticketing and services across the Rhine-Main metropolitan area in Germany.
  • C. Verkehrsverbund Ost-Region
    Verkehrsverbund Ost-Region is the public transport association that coordinates and manages integrated ticketing and fares for the eastern region of Austria, including Vienna and its surrounding areas.
  • D. Hamburger Verkehrsverbund
    Hamburger Verkehrsverbund is the integrated public transport association serving Hamburg and its surrounding metropolitan region in northern Germany.
  • E. Rhein-Neckar-Verkehr
    Rhein-Neckar-Verkehr is a regional public transport company operating buses and trams in the Rhine-Neckar metropolitan area of southwestern Germany.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Verkehrsverbund Rhein-Sieg
Target entity description: Verkehrsverbund Rhein-Sieg is a regional public transport association in the Rhine-Sieg area of Germany that coordinates and integrates fares and services across multiple transit operators.
  • A. Verkehrsverbund Rhein-Ruhr
    Verkehrsverbund Rhein-Ruhr is a major German public transport association that coordinates and integrates regional and local transit services across the Rhine-Ruhr metropolitan area in North Rhine-Westphalia.
  • B. Rhein-Main-Verkehrsverbund
    Rhein-Main-Verkehrsverbund is the regional public transport association that coordinates and manages integrated ticketing and services across the Rhine-Main metropolitan area in Germany.
  • C. Verkehrsverbund Ost-Region
    Verkehrsverbund Ost-Region is the public transport association that coordinates and manages integrated ticketing and fares for the eastern region of Austria, including Vienna and its surrounding areas.
  • D. Hamburger Verkehrsverbund
    Hamburger Verkehrsverbund is the integrated public transport association serving Hamburg and its surrounding metropolitan region in northern Germany.
  • E. Rhein-Neckar-Verkehr
    Rhein-Neckar-Verkehr is a regional public transport company operating buses and trams in the Rhine-Neckar metropolitan area of southwestern Germany.
  • F. None of above. chosen

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_69d8b9070cac81909fa9473fb1c3f1c7 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ccef022c81909be41b2c3a3ee68e completed April 19, 2026, 12:39 p.m.
Created at: April 10, 2026, 10:26 a.m.