Triple
T20861534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucerne–Immensee railway |
E513628
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Gotthard line at Immensee |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Gotthard line at Immensee | Statement: [Lucerne–Immensee railway, connectsTo, Gotthard line at Immensee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gotthard line at Immensee Context triple: [Lucerne–Immensee railway, connectsTo, Gotthard line at Immensee]
-
A.
Lucerne–Immensee railway
The Lucerne–Immensee railway is a Swiss standard-gauge main line connecting the city of Lucerne with Immensee, forming an important link in central Switzerland’s rail network.
-
B.
Zurich–Bern line
The Zurich–Bern line is a major Swiss railway corridor connecting the cities of Zurich and Bern and forming part of the country’s primary east–west rail axis.
-
C.
Lauterbrunnen–Interlaken line
The Lauterbrunnen–Interlaken line is a Swiss metre-gauge railway route in the Bernese Oberland that connects the resort town of Interlaken with the alpine village of Lauterbrunnen, serving as a key link in the Jungfrau region’s mountain railway network.
-
D.
Thun–Interlaken line
The Thun–Interlaken line is a standard-gauge railway in the Bernese Oberland region of Switzerland that connects the town of Thun with the resort area of Interlaken along the shores of Lake Thun.
-
E.
Interlaken–Grindelwald line
The Interlaken–Grindelwald line is a scenic Swiss railway route in the Bernese Oberland that connects the resort town of Interlaken with the mountain village of Grindelwald, serving as a key access line to the Jungfrau region.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Gotthard line at Immensee Target entity description: The Gotthard line at Immensee is a key junction on Switzerland’s north–south trans-Alpine railway corridor, linking the Lucerne–Immensee route to the main Gotthard railway line.
-
A.
Lucerne–Immensee railway
The Lucerne–Immensee railway is a Swiss standard-gauge main line connecting the city of Lucerne with Immensee, forming an important link in central Switzerland’s rail network.
-
B.
Zurich–Bern line
The Zurich–Bern line is a major Swiss railway corridor connecting the cities of Zurich and Bern and forming part of the country’s primary east–west rail axis.
-
C.
Lauterbrunnen–Interlaken line
The Lauterbrunnen–Interlaken line is a Swiss metre-gauge railway route in the Bernese Oberland that connects the resort town of Interlaken with the alpine village of Lauterbrunnen, serving as a key link in the Jungfrau region’s mountain railway network.
-
D.
Thun–Interlaken line
The Thun–Interlaken line is a standard-gauge railway in the Bernese Oberland region of Switzerland that connects the town of Thun with the resort area of Interlaken along the shores of Lake Thun.
-
E.
Interlaken–Grindelwald line
The Interlaken–Grindelwald line is a scenic Swiss railway route in the Bernese Oberland that connects the resort town of Interlaken with the mountain village of Grindelwald, serving as a key access line to the Jungfrau region.
- F. None of above. chosen
Provenance (2 batches)
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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3ad3d1c8190be2fe35a85f2447c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 12:44 p.m.