Triple
T20028831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow–Kursk railway line |
E495063
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Tula railway station |
—
|
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: Tula railway station | Statement: [Moscow–Kursk railway line, hasStation, Tula railway station]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tula railway station Context triple: [Moscow–Kursk railway line, hasStation, Tula railway station]
-
A.
Nikolaevsky railway station
Nikolaevsky railway station was the historical name of Moscow’s oldest mainline rail terminal, later known as Leningradsky railway terminal, which serves trains to Saint Petersburg and the northwest of Russia.
-
B.
Bytom Railway Station
Bytom Railway Station is a historic rail transport hub in the city of Bytom, Poland, serving as a key node in the region’s passenger and freight railway network.
-
C.
Tikhvin railway station
Tikhvin railway station is a regional rail transport hub serving the town of Tikhvin in Leningrad Oblast, Russia, on key routes connecting it with major cities.
-
D.
Plesetskaya railway station
Plesetskaya railway station is a regional rail hub in Arkhangelsk Oblast, Russia, serving the settlement of Plesetsk and connecting it to the broader Russian railway network.
-
E.
Paveletsky railway station
Paveletsky railway station is one of Moscow’s major rail terminals, serving long-distance, suburban, and high-speed trains and providing a key transport link between the city center and southern destinations.
- 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: Tula railway station Target entity description: Tula railway station is a major rail hub in the city of Tula, Russia, providing regional and long-distance passenger services and connecting the city with Moscow and other destinations.
-
A.
Nikolaevsky railway station
Nikolaevsky railway station was the historical name of Moscow’s oldest mainline rail terminal, later known as Leningradsky railway terminal, which serves trains to Saint Petersburg and the northwest of Russia.
-
B.
Bytom Railway Station
Bytom Railway Station is a historic rail transport hub in the city of Bytom, Poland, serving as a key node in the region’s passenger and freight railway network.
-
C.
Tikhvin railway station
Tikhvin railway station is a regional rail transport hub serving the town of Tikhvin in Leningrad Oblast, Russia, on key routes connecting it with major cities.
-
D.
Plesetskaya railway station
Plesetskaya railway station is a regional rail hub in Arkhangelsk Oblast, Russia, serving the settlement of Plesetsk and connecting it to the broader Russian railway network.
-
E.
Paveletsky railway station
Paveletsky railway station is one of Moscow’s major rail terminals, serving long-distance, suburban, and high-speed trains and providing a key transport link between the city center and southern destinations.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662908df081909a6c8ccf0dd90fff |
completed | April 20, 2026, 5:29 p.m. |
Created at: April 11, 2026, 3:36 p.m.