Triple

T10878977
Position Surface form Disambiguated ID Type / Status
Subject Komsomolskaya Square E256869 entity
Predicate hasNearbyMetroLine P33788 FINISHED
Object Koltsevaya line E44698 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: Koltsevaya line | Statement: [Komsomolskaya Square, hasNearbyMetroLine, Koltsevaya line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koltsevaya line
Context triple: [Komsomolskaya Square, hasNearbyMetroLine, Koltsevaya line]
  • A. Koltsevaya Line chosen
    The Koltsevaya Line is the circular line of the Moscow Metro, known for encircling the city center and connecting many of the system’s radial lines.
  • 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. Zhdanovskaya Line
    Zhdanovskaya Line was the former name of a line of the Moscow Metro, later known as the Tagansko–Krasnopresnenskaya Line.
  • E. 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.
  • 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_69d6aa848804819081b2713ca0bedf06 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d751ae92548190a3563c5b18650a32 completed April 9, 2026, 7:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69dff7e2322c8190a55605237ae6ce95 completed April 15, 2026, 8:41 p.m.
Created at: April 8, 2026, 9:21 p.m.