Triple
T21257323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zurich–Schaffhausen railway line |
E523902
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway infrastructure in Switzerland |
C3574
|
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: railway infrastructure in Switzerland Context triple: [Zurich–Schaffhausen railway line, instanceOf, railway infrastructure in Switzerland]
-
A.
transport association in Switzerland
A transport association in Switzerland is a regional organization that coordinates and integrates public transportation services, fares, and timetables across multiple operators within a defined area to provide seamless mobility for passengers.
-
B.
railway network
A railway network is an interconnected system of tracks, stations, signaling, and rolling stock that enables the organized movement of trains between multiple locations.
-
C.
transalpine railway
A transalpine railway is a rail line that crosses or traverses the Alps, typically using tunnels, viaducts, and mountain passes to connect regions on either side of the mountain range.
-
D.
railway infrastructure element
chosen
A railway infrastructure element is any physical component of a rail system—such as tracks, signals, switches, bridges, or platforms—that supports the safe and efficient operation of trains.
-
E.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:58 p.m.