Triple

T2108970
Position Surface form Disambiguated ID Type / Status
Subject Mayakovskaya E42459 entity
Predicate hasTransferTo P17241 FINISHED
Object Tverskaya station E281022 NE FINISHED

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: Tverskaya station | Statement: [Mayakovskaya, hasTransferTo, Tverskaya station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tverskaya station
Context triple: [Mayakovskaya, hasTransferTo, Tverskaya station]
  • A. Tverskaya metro station chosen
    Tverskaya metro station is a central Moscow Metro station on the Zamoskvoretskaya Line, known for serving the busy Tverskaya Street area near the city’s historic and commercial core.
  • B. Spasskaya metro station
    Spasskaya metro station is a Saint Petersburg Metro station that serves as a key transfer hub on the city’s network, located in the historic Admiralteysky District.
  • C. Lubyanka station
    Lubyanka station is a central Moscow Metro station known for its historical significance and proximity to the former KGB headquarters at Lubyanka Square.
  • D. Dzerzhinskaya station
    Dzerzhinskaya station is a stop on the Volgograd Metrotram light rail system in Volgograd, Russia.
  • E. Preobrazhenskaya Ploshchad station
    Preobrazhenskaya Ploshchad station is a Moscow Metro station serving the Preobrazhenskoye District in the northeastern part of the city.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69a8871040f08190aac2e2d0ab6b47ad completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abbae03f308190841f5a419bb821f6 completed March 7, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69b3544c5fcc8190b2d8d61449dfffb3 completed March 13, 2026, 12:03 a.m.
Created at: March 4, 2026, 7:43 p.m.