Triple

T19173455
Position Surface form Disambiguated ID Type / Status
Subject Saint Petersburg Moskovsky railway station E469382 entity
Predicate connectsWith P37 FINISHED
Object Kursk NE NERFINISHED

How this triple was built (2 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: Kursk | Statement: [Saint Petersburg Moskovsky railway station, connectsWith, Kursk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kursk
Context triple: [Saint Petersburg Moskovsky railway station, connectsWith, Kursk]
  • A. Kursk
    Kursk is a historic city in western Russia known for the pivotal World War II Battle of Kursk and its role as an important regional industrial and cultural center.
  • B. Kurskaya chosen
    Kurskaya is a Moscow Metro station on the Koltsevaya (Circle) Line, serving as a major transfer hub in the city’s rapid transit network.
  • C. Kronstadt
    Kronstadt is a historic Russian naval port and fortress city located on Kotlin Island near Saint Petersburg, long serving as a key base for the Russian Baltic Fleet.
  • D. Kronstadt
    Kronstadt is a historic Transylvanian city (now known as Brașov, Romania) renowned for its medieval fortifications and Saxon heritage.
  • E. Petrovsk-Port
    Petrovsk-Port was a significant port city in the Russian Empire’s Caucasus region, serving as an important commercial and strategic hub on the Caspian Sea.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8dd09d5a081909ae43c286651ae5a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f16613dc8190987c2d79dc616e40 completed April 20, 2026, 9:27 a.m.
Created at: April 10, 2026, 12:06 p.m.