Triple

T1946803
Position Surface form Disambiguated ID Type / Status
Subject Big Circle Line E42071 entity
Predicate connectsWith P37 FINISHED
Object Butovskaya Line E47280 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: Butovskaya Line | Statement: [Big Circle Line, connectsWith, Butovskaya Line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Butovskaya Line
Context triple: [Big Circle Line, connectsWith, Butovskaya Line]
  • A. Butovskaya Line chosen
    The Butovskaya Line is a light metro line in the Moscow Metro system serving the Butovo district in the city’s south.
  • 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. 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.
  • D. 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.
  • E. Koltsevaya Line
    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.
  • 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_69a8870e08fc8190a319cbf2600db15f completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb32ebae881908f7541301f0198ae completed March 7, 2026, 5:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae03180a248190a0df96066923728a completed March 8, 2026, 11:15 p.m.
Created at: March 4, 2026, 7:36 p.m.