Triple

T20497894
Position Surface form Disambiguated ID Type / Status
Subject Lehel district E502920 entity
Predicate transportServedBy P1298 FINISHED
Object Munich U-Bahn line U5 — 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 U-Bahn line U5 | Statement: [Lehel district, transportServedBy, Munich U-Bahn line U5]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Munich U-Bahn line U5
Context triple: [Lehel district, transportServedBy, Munich U-Bahn line U5]
  • A. Munich U-Bahn line U4
    Munich U-Bahn line U4 is a rapid transit line in Munich’s underground railway network that runs east–west through the city, connecting central stations with several eastern districts.
  • B. Munich U-Bahn line U3
    Munich U-Bahn line U3 is a major rapid transit route in Munich’s underground network, running north–south across the city and serving numerous residential and commercial districts.
  • C. Berlin U-Bahn line U5
    Berlin U-Bahn line U5 is a major underground metro line in Berlin that runs east–west across the city, connecting central hubs like Alexanderplatz and Brandenburger Tor with eastern districts such as Lichtenberg and Hönow.
  • D. Munich U-Bahn
    The Munich U-Bahn is the German city's rapid transit metro system, forming a core part of its public transportation network with multiple underground lines serving urban and suburban areas.
  • E. Nuremberg U-Bahn
    The Nuremberg U-Bahn is the rapid transit system serving Nuremberg and its surrounding area in Germany, known for being one of the first networks to operate fully automated driverless trains.
  • 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 U-Bahn line U5
Target entity description: Munich U-Bahn line U5 is a major rapid transit route in Munich’s underground network, running east–west through the city and connecting central districts with outlying residential areas.
  • A. Munich U-Bahn line U4
    Munich U-Bahn line U4 is a rapid transit line in Munich’s underground railway network that runs east–west through the city, connecting central stations with several eastern districts.
  • B. Munich U-Bahn line U3
    Munich U-Bahn line U3 is a major rapid transit route in Munich’s underground network, running north–south across the city and serving numerous residential and commercial districts.
  • C. Berlin U-Bahn line U5
    Berlin U-Bahn line U5 is a major underground metro line in Berlin that runs east–west across the city, connecting central hubs like Alexanderplatz and Brandenburger Tor with eastern districts such as Lichtenberg and Hönow.
  • D. Munich U-Bahn
    The Munich U-Bahn is the German city's rapid transit metro system, forming a core part of its public transportation network with multiple underground lines serving urban and suburban areas.
  • E. Nuremberg U-Bahn
    The Nuremberg U-Bahn is the rapid transit system serving Nuremberg and its surrounding area in Germany, known for being one of the first networks to operate fully automated driverless trains.
  • 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_69e0b4b0373881909dd3e9387f82eab4 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69cbefe4c819098af5bfd4d92341d completed April 20, 2026, 9:38 p.m.
Created at: April 16, 2026, 11:35 a.m.