Triple
T20688223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basel–Bern railway line |
E508478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway in Switzerland |
C22714
|
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 in Switzerland Context triple: [Basel–Bern railway line, instanceOf, railway 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.
Rhaetian Railway station
A Rhaetian Railway station is a designated stop or terminal along the Rhaetian Railway network in Switzerland, providing passenger access, boarding, alighting, and related rail services on its regional and scenic routes.
-
C.
transalpine railway
chosen
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.
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.
-
E.
bridge in Switzerland
A bridge in Switzerland is a structural construction that spans physical obstacles such as rivers, valleys, or roads within Swiss territory, facilitating transportation and connectivity while often reflecting the country's engineering precision and alpine landscape.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:45 a.m.