Triple

T18322476
Position Surface form Disambiguated ID Type / Status
Subject Lodeynopolsky District E438916 entity
Predicate partOfHistoricalRoute P6309 FINISHED
Object Saint Petersburg–Arkhangelsk route 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: Saint Petersburg–Arkhangelsk route | Statement: [Lodeynopolsky District, partOfHistoricalRoute, Saint Petersburg–Arkhangelsk route]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saint Petersburg–Arkhangelsk route
Context triple: [Lodeynopolsky District, partOfHistoricalRoute, Saint Petersburg–Arkhangelsk route]
  • A. Saint Petersburg–Sortavala route
    The Saint Petersburg–Sortavala route is a regional transport corridor in northwestern Russia connecting the city of Saint Petersburg with the Karelian town of Sortavala, passing through intermediate localities such as Priozersk.
  • B. Moscow–St. Petersburg corridor
    The Moscow–St. Petersburg corridor is a major transportation axis in Russia that links the country’s capital with its second-largest city through a dense network of road and rail infrastructure.
  • C. Saint Petersburg–Vyborg railway
    The Saint Petersburg–Vyborg railway is a major rail line in northwestern Russia connecting Saint Petersburg with the city of Vyborg and serving as part of the route toward Finland.
  • D. Murmansk Railway
    Murmansk Railway is a major rail line in northwestern Russia that connects the Arctic port city of Murmansk and the Kola Peninsula with the broader Russian railway network.
  • E. 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.
  • 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: Saint Petersburg–Arkhangelsk route
Target entity description: The Saint Petersburg–Arkhangelsk route is a historic transportation corridor in northwestern Russia that connected the imperial capital of Saint Petersburg with the northern port city of Arkhangelsk.
  • A. Saint Petersburg–Sortavala route
    The Saint Petersburg–Sortavala route is a regional transport corridor in northwestern Russia connecting the city of Saint Petersburg with the Karelian town of Sortavala, passing through intermediate localities such as Priozersk.
  • B. Moscow–St. Petersburg corridor
    The Moscow–St. Petersburg corridor is a major transportation axis in Russia that links the country’s capital with its second-largest city through a dense network of road and rail infrastructure.
  • C. Saint Petersburg–Vyborg railway
    The Saint Petersburg–Vyborg railway is a major rail line in northwestern Russia connecting Saint Petersburg with the city of Vyborg and serving as part of the route toward Finland.
  • D. Murmansk Railway
    Murmansk Railway is a major rail line in northwestern Russia that connects the Arctic port city of Murmansk and the Kola Peninsula with the broader Russian railway network.
  • E. 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.
  • 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_69d8b916a2d081909e249e4902f6aad9 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50aa7be288190983f13e9c7061b6d completed April 19, 2026, 5:02 p.m.
Created at: April 10, 2026, 10:36 a.m.