Triple

T20556078
Position Surface form Disambiguated ID Type / Status
Subject Ludwigsvorstadt-Isarvorstadt E504722 entity
Predicate publicTransport P1288 FINISHED
Object Munich U-Bahn lines 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 lines U5 | Statement: [Ludwigsvorstadt-Isarvorstadt, publicTransport, Munich U-Bahn lines U5]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Munich U-Bahn lines U5
Context triple: [Ludwigsvorstadt-Isarvorstadt, publicTransport, Munich U-Bahn lines U5]
  • A. Munich U-Bahn lines U3 and U6
    The Munich U-Bahn lines U3 and U6 are two of the city’s main rapid transit routes, running north–south through central Munich and intersecting at the busy Marienplatz station.
  • B. 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.
  • 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. U5 line of Frankfurt U-Bahn
    The U5 line of the Frankfurt U-Bahn is an urban rail route in Frankfurt am Main that connects central districts with the northeastern parts of the city as part of the city’s rapid transit network.
  • E. 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.
  • 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 lines U5
Target entity description: Munich U-Bahn lines U5 is a major rapid transit line in Munich’s underground network, connecting central districts with outlying residential areas and key transport hubs.
  • A. Munich U-Bahn line U5 chosen
    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.
  • B. Munich U-Bahn lines U3 and U6
    The Munich U-Bahn lines U3 and U6 are two of the city’s main rapid transit routes, running north–south through central Munich and intersecting at the busy Marienplatz station.
  • C. 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.
  • D. 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.
  • E. U5 line of Frankfurt U-Bahn
    The U5 line of the Frankfurt U-Bahn is an urban rail route in Frankfurt am Main that connects central districts with the northeastern parts of the city as part of the city’s rapid transit network.
  • F. None of above.

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_69e0b4b6587c8190aee63dc7cff244ea completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a5dd02588190abddfcb868259a38 completed April 20, 2026, 10:17 p.m.
Created at: April 16, 2026, 11:38 a.m.