Triple
T22720394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Großhadern |
E561842
|
entity |
| Predicate | hasPublicTransportConnection |
P3791
|
FINISHED |
| Object | Munich U-Bahn line U6 |
—
|
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 U6 | Statement: [Großhadern, hasPublicTransportConnection, Munich U-Bahn line U6]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Munich U-Bahn line U6 Context triple: [Großhadern, hasPublicTransportConnection, Munich U-Bahn line U6]
-
A.
Munich U-Bahn line U5
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 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.
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.
-
D.
Berlin U-Bahn line U6
Berlin U-Bahn line U6 is a major north–south underground metro line in Berlin that connects the northern district of Tegel with southern neighborhoods through the city center.
-
E.
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.
- 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 U6 Target entity description: Munich U-Bahn line U6 is a major north–south subway line in Munich’s rapid transit network, connecting the city center with northern districts and southern areas including the university and hospital quarter near Großhadern.
-
A.
Munich U-Bahn line U5
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 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.
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.
-
D.
Berlin U-Bahn line U6
Berlin U-Bahn line U6 is a major north–south underground metro line in Berlin that connects the northern district of Tegel with southern neighborhoods through the city center.
-
E.
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.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17910deb48190b38174e16868f3dd |
completed | April 29, 2026, 3:20 a.m. |
Created at: April 17, 2026, 3:19 p.m.