Triple

T9826358
Position Surface form Disambiguated ID Type / Status
Subject Tagansko–Krasnopresnenskaya Line E238662 entity
Predicate hasFormerName P65 FINISHED
Object Zhdanovskaya Line E238662 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: Zhdanovskaya Line | Statement: [Tagansko–Krasnopresnenskaya Line, hasFormerName, Zhdanovskaya Line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zhdanovskaya Line
Context triple: [Tagansko–Krasnopresnenskaya Line, hasFormerName, Zhdanovskaya Line]
  • A. Zhdanovskaya Line chosen
    Zhdanovskaya Line was the former name of a line of the Moscow Metro, later known as the Tagansko–Krasnopresnenskaya Line.
  • B. Butovskaya Line
    The Butovskaya Line is a light metro line in the Moscow Metro system serving the Butovo district in the city’s south.
  • C. Sokolnicheskaya Line
    The Sokolnicheskaya Line is one of the oldest and most important lines of the Moscow Metro, running generally north–south and serving several central and historic districts of the city.
  • D. Nekrasovskaya Line
    The Nekrasovskaya Line is a line of the Moscow Metro system serving the southeastern districts of Moscow with modern, high-capacity rapid transit.
  • E. Solntsevskaya Line
    The Solntsevskaya Line is a line of the Moscow Metro system serving western and southwestern districts of Moscow with modern rapid transit connections.
  • 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_69ca84e0dd1881909800765d1e21f735 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb32370e8819087c85fb8328587be completed April 2, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2b5aab5408190aacdc310222bb85b completed April 5, 2026, 7:19 p.m.
Created at: March 30, 2026, 8:32 p.m.