Triple

T21324960
Position Surface form Disambiguated ID Type / Status
Subject Bryansk E525726 entity
Predicate hasRailwayStation P918 FINISHED
Object Bryansk-Orlovsky 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: Bryansk-Orlovsky railway station | Statement: [Bryansk, hasRailwayStation, Bryansk-Orlovsky railway station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bryansk-Orlovsky railway station
Context triple: [Bryansk, hasRailwayStation, Bryansk-Orlovsky railway station]
  • A. Oryol railway station
    Oryol railway station is a major rail hub in the city of Oryol, Russia, serving long-distance and regional passenger traffic on key routes in western Russia.
  • B. 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.
  • C. Petrovsko-Razumovskaya railway station
    Petrovsko-Razumovskaya railway station is a passenger rail stop in Moscow that serves the Petrovsko-Razumovskaya area and connects it to the wider suburban and urban rail network.
  • D. 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.
  • E. Yaroslavl-Glavny railway station
    Yaroslavl-Glavny railway station is the main rail terminal in Yaroslavl, Russia, serving as a key hub for regional and long-distance passenger trains.
  • 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: Bryansk-Orlovsky railway station
Target entity description: Bryansk-Orlovsky railway station is the main railway hub in Bryansk, Russia, serving as a key junction for regional and long-distance passenger and freight trains.
  • A. Oryol railway station
    Oryol railway station is a major rail hub in the city of Oryol, Russia, serving long-distance and regional passenger traffic on key routes in western Russia.
  • B. 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.
  • C. Petrovsko-Razumovskaya railway station
    Petrovsko-Razumovskaya railway station is a passenger rail stop in Moscow that serves the Petrovsko-Razumovskaya area and connects it to the wider suburban and urban rail network.
  • D. 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.
  • E. Yaroslavl-Glavny railway station
    Yaroslavl-Glavny railway station is the main rail terminal in Yaroslavl, Russia, serving as a key hub for regional and long-distance passenger trains.
  • 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_69e0b51b90788190a4dd823d962626da completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e77ed7732c8190a0e7aec6e7cbcef2 completed April 21, 2026, 1:42 p.m.
Created at: April 16, 2026, 4:41 p.m.