Triple

T11267004
Position Surface form Disambiguated ID Type / Status
Subject Ligovsky Prospekt metro station E266711 entity
Predicate partOfLine P6309 FINISHED
Object Pravoberezhnaya Line E617240 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: Pravoberezhnaya Line | Statement: [Ligovsky Prospekt metro station, partOfLine, Pravoberezhnaya Line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pravoberezhnaya Line
Context triple: [Ligovsky Prospekt metro station, partOfLine, Pravoberezhnaya Line]
  • A. Pravoberezhnaya Line chosen
    The Pravoberezhnaya Line is one of the main rapid transit lines of the Saint Petersburg Metro, serving the city’s right-bank districts.
  • B. Filevskaya Line
    Filevskaya Line is one of the lines of the Moscow Metro, known for its partially surface-level sections and service to western districts of the city.
  • C. Butovskaya Line
    The Butovskaya Line is a light metro line in the Moscow Metro system serving the Butovo district in the city’s south.
  • D. 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.
  • E. Zhdanovskaya Line
    Zhdanovskaya Line was the former name of a line of the Moscow Metro, later known as the Tagansko–Krasnopresnenskaya Line.
  • 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_69d6aac8c2f48190ad0596f1f89f0470 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e94e5e3c8190a31995d55d20d7ed completed April 9, 2026, 6 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5258cc5208190be268ac6a82c9419 completed April 19, 2026, 6:57 p.m.
Created at: April 8, 2026, 9:31 p.m.