Triple
T38561657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U8 (Munich U-Bahn) |
E928091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Munich U-Bahn line designation |
C55679
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Munich U-Bahn line designation Context triple: [U8 (Munich U-Bahn), instanceOf, Munich U-Bahn line designation]
-
A.
Munich U-Bahn line
chosen
A Munich U-Bahn line is a designated rapid transit route within Munich’s underground railway network, defined by its specific path, stations, service frequency, and operational characteristics.
-
B.
Hamburg U-Bahn line
A Hamburg U-Bahn line is a designated rapid transit route within Hamburg’s underground and elevated metro network, defined by its sequence of stations, track alignment, and service pattern.
-
C.
Munich U-Bahn station
A Munich U-Bahn station is an underground or surface-level transit facility in Munich’s rapid transit network where passengers access, board, and transfer between U-Bahn trains.
-
D.
Vienna U-Bahn line
A Vienna U-Bahn line is a specific rapid transit route within Vienna’s underground railway network, defined by its track alignment, served stations, operating schedule, and rolling stock.
-
E.
Munich S-Bahn station
A Munich S-Bahn station is a railway facility within the Munich suburban rapid transit network where S-Bahn trains stop to allow passengers to board, alight, and transfer between local and regional services.
- F. None of above.
Provenance (1 batch)
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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.