Triple
T31424831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankfurt tram line 16 |
E801631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Frankfurt am Main tram route |
C58834
|
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 am Main tram route Context triple: [Frankfurt tram line 16, instanceOf, Frankfurt am Main tram route]
-
A.
road in Frankfurt am Main
A road in Frankfurt am Main is a public thoroughfare within the city’s urban and suburban areas that facilitates vehicular, bicycle, and pedestrian traffic while connecting residential, commercial, and industrial zones.
-
B.
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.
-
C.
Stuttgart S-Bahn line
A Stuttgart S-Bahn line is a specific rapid transit route within the Stuttgart metropolitan rail network that connects designated suburban and urban stations according to a defined timetable and service pattern.
-
D.
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.
-
E.
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.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 8:52 p.m.