Triple

T22870232
Position Surface form Disambiguated ID Type / Status
Subject Heidelberg tram network E567171 entity
Predicate fareSystem P395 FINISHED
Object Verkehrsverbund Rhein-Neckar 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-Neckar | Statement: [Heidelberg tram network, fareSystem, Verkehrsverbund Rhein-Neckar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Verkehrsverbund Rhein-Neckar
Context triple: [Heidelberg tram network, fareSystem, Verkehrsverbund Rhein-Neckar]
  • A. 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.
  • B. 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.
  • C. Verkehrsverbund Rhein-Sieg
    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.
  • D. Karlsruher Verkehrsverbund
    Karlsruher Verkehrsverbund is a regional public transport association in and around Karlsruhe, Germany, that coordinates and integrates fares and services across multiple transit operators.
  • E. 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.
  • 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-Neckar
Target entity description: Verkehrsverbund Rhein-Neckar is a regional public transport association in southwestern Germany that coordinates and integrates fares and services across multiple transit operators in the Rhine-Neckar metropolitan area.
  • A. 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.
  • B. 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.
  • C. Verkehrsverbund Rhein-Sieg
    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.
  • D. Karlsruher Verkehrsverbund
    Karlsruher Verkehrsverbund is a regional public transport association in and around Karlsruhe, Germany, that coordinates and integrates fares and services across multiple transit operators.
  • E. 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.
  • 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_69e24589d8348190b96422d13a678bc1 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17f04b06481909004818ec8fc5a26 completed April 29, 2026, 3:46 a.m.
Created at: April 17, 2026, 3:38 p.m.