Triple
T14730777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenvers station |
E346067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mountain railway terminus |
C35079
|
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: mountain railway terminus Context triple: [Montenvers station, instanceOf, mountain railway terminus]
-
A.
narrow-gauge railway terminus
A narrow-gauge railway terminus is the end station or final stopping point on a railway line that uses tracks of narrower width than the standard gauge, where trains begin or conclude their journeys and related operations are managed.
-
B.
cable car station
A cable car station is a designated facility where passengers board, disembark, and transfer between cable-propelled vehicles, typically featuring platforms, ticketing areas, and equipment for operating and maintaining the cable system.
-
C.
mountain station
A mountain station is a facility or settlement located at a high elevation in mountainous terrain, typically serving as a base for transportation, research, tourism, or outdoor activities.
-
D.
mountain rack railway
A mountain rack railway is a steep-gradient railway system that uses a toothed rack rail engaged by a cogwheel on the train to provide additional traction and braking on mountainous terrain.
-
E.
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.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:29 a.m.