Triple
T29061840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig City Tunnel |
E735556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | underground railway link |
C21697
|
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: underground railway link Context triple: [Leipzig City Tunnel, instanceOf, underground railway link]
-
A.
underground rail corridor
chosen
An underground rail corridor is a subsurface passageway engineered to safely guide trains between stations, housing tracks, utilities, and supporting infrastructure while minimizing surface disruption.
-
B.
cross-London rail system
A cross-London rail system is an integrated network of rail lines and tunnels that traverse the city from one side to the other, providing high-capacity, rapid transit across central London and connecting outer suburbs.
-
C.
subway line
A subway line is a fixed route within an urban rail transit system, consisting of a sequence of stations and tracks over which trains operate according to a scheduled service.
-
D.
urban rail loop line
An urban rail loop line is a circular or near-circular transit route within a city that connects multiple districts and intersecting lines, allowing continuous, bidirectional travel without a terminal endpoint.
-
E.
ground transportation link
A ground transportation link is a physical connection, such as a road, rail line, or dedicated corridor, that enables the movement of people or goods between two or more locations on land.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:15 a.m.