Triple
T20710547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Russian train at Pskov railway station |
E509024
|
entity |
| Predicate | railwayLine |
P848
|
FINISHED |
| Object | Pskov–Vyatka railway network |
—
|
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: Pskov–Vyatka railway network | Statement: [Imperial Russian train at Pskov railway station, railwayLine, Pskov–Vyatka railway network]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pskov–Vyatka railway network Context triple: [Imperial Russian train at Pskov railway station, railwayLine, Pskov–Vyatka railway network]
-
A.
Privolzhskaya Railway
Privolzhskaya Railway is a regional division of the Russian Railways network that operates rail services and infrastructure across the Volga region of Russia.
-
B.
Bologoye–Rybinsk railway line
The Bologoye–Rybinsk railway line is a regional rail route in western Russia that connects the towns of Bologoye and Rybinsk, serving intermediate localities such as Udomlya.
-
C.
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.
-
D.
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.
-
E.
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.
- 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: Pskov–Vyatka railway network Target entity description: The Pskov–Vyatka railway network was a major Imperial Russian rail system connecting the northwestern city of Pskov with the Vyatka region, facilitating long-distance transport and regional development.
-
A.
Privolzhskaya Railway
Privolzhskaya Railway is a regional division of the Russian Railways network that operates rail services and infrastructure across the Volga region of Russia.
-
B.
Bologoye–Rybinsk railway line
The Bologoye–Rybinsk railway line is a regional rail route in western Russia that connects the towns of Bologoye and Rybinsk, serving intermediate localities such as Udomlya.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1974ba08190b0e5ad529be95e4c |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 12:14 p.m.