Triple
T17281609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazansky railway terminal |
E419541
|
entity |
| Predicate | railwayLineTerminusFor |
P77374
|
FINISHED |
| Object |
Moscow–Kazan railway
The Moscow–Kazan railway is a major Russian rail line connecting the capital Moscow with the city of Kazan, serving as an important corridor for passenger and freight transport in the Volga region.
|
E1271399
|
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: Moscow–Kazan railway | Statement: [Kazansky railway terminal, railwayLineTerminusFor, Moscow–Kazan railway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moscow–Kazan railway Context triple: [Kazansky railway terminal, railwayLineTerminusFor, Moscow–Kazan railway]
-
A.
Moscow–Samara railway line
The Moscow–Samara railway line is a major Russian rail route connecting the capital Moscow with the Volga city of Samara, serving as an important corridor for both passenger and freight transport.
-
B.
Moscow–Nizhny Novgorod railway
The Moscow–Nizhny Novgorod railway is a major Russian rail corridor connecting the capital Moscow with the important Volga city of Nizhny Novgorod, serving as a key route for both passenger and freight traffic.
-
C.
Moscow–Minsk railway
The Moscow–Minsk railway is a major international rail line connecting Russia’s capital Moscow with Belarus’s capital Minsk, serving as a key transport corridor between the two countries and further into Europe.
-
D.
Moscow–Yaroslavl railway line
The Moscow–Yaroslavl railway line is a major rail route in Russia connecting Moscow with the historic city of Yaroslavl and serving as part of the broader network linking the capital to the northeast.
-
E.
Moscow–Kursk railway line
The Moscow–Kursk railway line is a major rail route in western Russia that connects Moscow with the city of Kursk and serves numerous intermediate towns and suburbs.
- 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: Moscow–Kazan railway Triple: [Kazansky railway terminal, railwayLineTerminusFor, Moscow–Kazan railway]
Generated description
The Moscow–Kazan railway is a major Russian rail line connecting the capital Moscow with the city of Kazan, serving as an important corridor for passenger and freight transport in the Volga region.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Moscow–Kazan railway Target entity description: The Moscow–Kazan railway is a major Russian rail line connecting the capital Moscow with the city of Kazan, serving as an important corridor for passenger and freight transport in the Volga region.
-
A.
Moscow–Samara railway line
The Moscow–Samara railway line is a major Russian rail route connecting the capital Moscow with the Volga city of Samara, serving as an important corridor for both passenger and freight transport.
-
B.
Moscow–Nizhny Novgorod railway
The Moscow–Nizhny Novgorod railway is a major Russian rail corridor connecting the capital Moscow with the important Volga city of Nizhny Novgorod, serving as a key route for both passenger and freight traffic.
-
C.
Moscow–Minsk railway
The Moscow–Minsk railway is a major international rail line connecting Russia’s capital Moscow with Belarus’s capital Minsk, serving as a key transport corridor between the two countries and further into Europe.
-
D.
Moscow–Yaroslavl railway line
The Moscow–Yaroslavl railway line is a major rail route in Russia connecting Moscow with the historic city of Yaroslavl and serving as part of the broader network linking the capital to the northeast.
-
E.
Moscow–Kursk railway line
The Moscow–Kursk railway line is a major rail route in western Russia that connects Moscow with the city of Kursk and serves numerous intermediate towns and suburbs.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayLineTerminusFor Context triple: [Kazansky railway terminal, railwayLineTerminusFor, Moscow–Kazan railway]
-
A.
railLineTerminus
Indicates that a rail line ends or terminates at the specified location or station.
-
B.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
C.
railTerminus
chosen
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
-
D.
railwayUpperTerminus
Indicates that a railway line or route reaches its upper (typically higher-altitude or upstream) terminal endpoint at the related location.
-
E.
railwayStationFor
Indicates a relationship where a railway station serves, is designated for, or primarily associated with a particular place, line, or service.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4332a4c008190b44f4145d0e94a21 |
completed | April 19, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01c1e9985c8190861ddd9eced1414b |
completed | May 11, 2026, 11:47 a.m. |
| NEDg | Description generation | batch_6a01c2e2f3988190af955c99d5dd7c90 |
completed | May 11, 2026, 11:52 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a01c330dbe88190ab9a594523653a10 |
completed | May 11, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.