Triple
T4986667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lausanne–Bern railway line |
E112019
|
entity |
| Predicate | formsSectionOf |
P3120
|
FINISHED |
| Object |
Lausanne–Olten main line
The Lausanne–Olten main line is a key Swiss railway corridor linking western Switzerland with the central rail hub of Olten and forming part of the country’s primary east–west rail axis.
|
E493311
|
NE FINISHED |
How this triple was built (5 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: Lausanne–Olten main line | Statement: [Lausanne–Bern railway line, formsSectionOf, Lausanne–Olten main line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lausanne–Olten main line Context triple: [Lausanne–Bern railway line, formsSectionOf, Lausanne–Olten main line]
-
A.
Geneva–Lausanne–Bern–Zurich main line
The Geneva–Lausanne–Bern–Zurich main line is a major Swiss railway corridor that connects key cities across western and central Switzerland and forms part of the country’s primary east–west rail axis.
-
B.
Lausanne–Geneva railway line
The Lausanne–Geneva railway line is a major Swiss rail corridor connecting the cities of Lausanne and Geneva along the northern shore of Lake Geneva, serving as a key route for both regional and international trains.
-
C.
Bern–Neuchâtel railway line
The Bern–Neuchâtel railway line is a key Swiss standard-gauge route connecting the federal city of Bern with Neuchâtel, serving both regional and intercity passenger traffic.
-
D.
Basel–Olten railway line
The Basel–Olten railway line is a major Swiss rail corridor linking the city of Basel with the central hub of Olten, forming part of a key national and international transit route.
-
E.
Vevey–Montreux railway line
The Vevey–Montreux railway line is a Swiss standard-gauge rail route along the shores of Lake Geneva that connects the towns of Vevey and Montreux and forms part of an important regional and tourist transport corridor.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Lausanne–Olten main line Triple: [Lausanne–Bern railway line, formsSectionOf, Lausanne–Olten main line]
Generated description
The Lausanne–Olten main line is a key Swiss railway corridor linking western Switzerland with the central rail hub of Olten and forming part of the country’s primary east–west rail axis.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Lausanne–Olten main line Target entity description: The Lausanne–Olten main line is a key Swiss railway corridor linking western Switzerland with the central rail hub of Olten and forming part of the country’s primary east–west rail axis.
-
A.
Geneva–Lausanne–Bern–Zurich main line
The Geneva–Lausanne–Bern–Zurich main line is a major Swiss railway corridor that connects key cities across western and central Switzerland and forms part of the country’s primary east–west rail axis.
-
B.
Lausanne–Geneva railway line
The Lausanne–Geneva railway line is a major Swiss rail corridor connecting the cities of Lausanne and Geneva along the northern shore of Lake Geneva, serving as a key route for both regional and international trains.
-
C.
Bern–Neuchâtel railway line
The Bern–Neuchâtel railway line is a key Swiss standard-gauge route connecting the federal city of Bern with Neuchâtel, serving both regional and intercity passenger traffic.
-
D.
Basel–Olten railway line
The Basel–Olten railway line is a major Swiss rail corridor linking the city of Basel with the central hub of Olten, forming part of a key national and international transit route.
-
E.
Vevey–Montreux railway line
The Vevey–Montreux railway line is a Swiss standard-gauge rail route along the shores of Lake Geneva that connects the towns of Vevey and Montreux and forms part of an important regional and tourist transport corridor.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsSectionOf Context triple: [Lausanne–Bern railway line, formsSectionOf, Lausanne–Olten main line]
-
A.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
B.
sectionType
Indicates the specific kind or category of section that an entity belongs to or represents.
-
C.
formsDivisionWith
Indicates that one entity combines with another to create or constitute a division or subgroup within a larger organization or structure.
-
D.
operatorInSection
Indicates that an operator is assigned to, works within, or is responsible for a specific section.
-
E.
divisionOrStructure
Indicates a relationship where one entity is an internal division, department, or structural subunit that is organizationally contained within another entity.
- F. None of above.
Provenance (6 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69beba546a1081909fe082663ad5e238 |
completed | March 21, 2026, 3:33 p.m. |
| NEDg | Description generation | batch_69bebc21b21c8190ad1c234ecbb8d431 |
completed | March 21, 2026, 3:41 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69bebc71065881908b27a2808fc4e630 |
completed | March 21, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.