Triple
T36178323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U4 train (Frankfurt rolling stock) |
E1046638
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Frankfurt U-Bahn rolling stock |
C63376
|
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: Frankfurt U-Bahn rolling stock Context triple: [U4 train (Frankfurt rolling stock), instanceOf, Frankfurt U-Bahn rolling stock]
-
A.
Nuremberg U-Bahn rolling stock
Nuremberg U-Bahn rolling stock comprises the various types of electric multiple unit trains specifically designed and operated for passenger service on the Nuremberg, Germany, underground rail network.
-
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.
Berlin U-Bahn facility
A Berlin U-Bahn facility is any physical structure, station, depot, or related infrastructure element that supports the operation, maintenance, or use of Berlin’s underground rapid transit system.
-
D.
Munich U-Bahn line
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.
-
E.
Frankfurt U-Bahn station
A Frankfurt U-Bahn station is an underground or surface-level transit facility in Frankfurt am Main where passengers access, board, and transfer between urban metro trains on the city's U-Bahn network.
- F. None of above. chosen
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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.