Triple

T21328647
Position Surface form Disambiguated ID Type / Status
Subject Fürstenfeldbruck E525834 entity
Predicate hasRailConnection P848 FINISHED
Object Munich–Augsburg railway 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: Munich–Augsburg railway | Statement: [Fürstenfeldbruck, hasRailConnection, Munich–Augsburg railway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Munich–Augsburg railway
Context triple: [Fürstenfeldbruck, hasRailConnection, Munich–Augsburg railway]
  • A. Munich–Regensburg railway
    The Munich–Regensburg railway is a major rail line in Bavaria, Germany, linking Munich with Regensburg and serving important intermediate cities such as Freising.
  • B. Nuremberg–Augsburg railway
    The Nuremberg–Augsburg railway is a major rail route in Bavaria, Germany, connecting the cities of Nuremberg and Augsburg and serving as an important corridor for both regional and long-distance passenger and freight traffic.
  • C. Munich–Rosenheim railway line
    The Munich–Rosenheim railway line is a major rail route in Bavaria, Germany, connecting Munich with Rosenheim and serving as an important corridor for regional, long-distance, and international train services.
  • D. Ulm–Augsburg railway
    The Ulm–Augsburg railway is a major rail line in southern Germany that connects the cities of Ulm and Augsburg and forms part of an important east–west transport corridor.
  • E. Nuremberg–Bamberg railway
    The Nuremberg–Bamberg railway is a major German main line in Bavaria that connects the cities of Nuremberg and Bamberg and forms part of important regional and long-distance rail routes.
  • 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: Munich–Augsburg railway
Target entity description: The Munich–Augsburg railway is one of Germany’s oldest and busiest mainline routes, connecting the Bavarian capital Munich with the city of Augsburg as a key regional and long-distance transport corridor.
  • A. Munich–Regensburg railway
    The Munich–Regensburg railway is a major rail line in Bavaria, Germany, linking Munich with Regensburg and serving important intermediate cities such as Freising.
  • B. Nuremberg–Augsburg railway
    The Nuremberg–Augsburg railway is a major rail route in Bavaria, Germany, connecting the cities of Nuremberg and Augsburg and serving as an important corridor for both regional and long-distance passenger and freight traffic.
  • C. Munich–Rosenheim railway line
    The Munich–Rosenheim railway line is a major rail route in Bavaria, Germany, connecting Munich with Rosenheim and serving as an important corridor for regional, long-distance, and international train services.
  • D. Ulm–Augsburg railway
    The Ulm–Augsburg railway is a major rail line in southern Germany that connects the cities of Ulm and Augsburg and forms part of an important east–west transport corridor.
  • E. Nuremberg–Bamberg railway
    The Nuremberg–Bamberg railway is a major German main line in Bavaria that connects the cities of Nuremberg and Bamberg and forms part of important regional and long-distance rail routes.
  • 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_69e0b51b90788190a4dd823d962626da completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7ab4e88848190b6efe85a4c8cd85a completed April 21, 2026, 4:52 p.m.
Created at: April 16, 2026, 4:42 p.m.