Triple

T2331591
Position Surface form Disambiguated ID Type / Status
Subject Arbatsko–Pokrovskaya Line E44213 entity
Predicate hasStation P35 FINISHED
Object Kievskaya E51121 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: Kievskaya | Statement: [Arbatsko–Pokrovskaya Line, hasStation, Kievskaya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kievskaya
Context triple: [Arbatsko–Pokrovskaya Line, hasStation, Kievskaya]
  • A. Kievskaya chosen
    Kievskaya is a prominent Moscow Metro station complex known for its ornate, Ukrainian-themed architecture and role as a major transfer hub.
  • B. Novoslobodskaya
    Novoslobodskaya is a Moscow Metro station famed for its distinctive stained-glass panels and ornate, cathedral-like interior design.
  • C. Kalinin
    Kalinin is the former Soviet-era name of the Russian city now known as Tver, reflecting its renaming in honor of Bolshevik leader Mikhail Kalinin.
  • D. Kakhovskaya
    Kakhovskaya is a Moscow Metro station that serves as part of the city’s Big Circle Line.
  • E. Krasnopresnenskaya
    Krasnopresnenskaya is a Moscow Metro station on the city’s circular Koltsevaya Line, known for its deep-level construction and Soviet-era architectural design.
  • 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_69a889132b488190bbb43ad4780ddd92 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abc669956881908b8d9784d6a06acf completed March 7, 2026, 6:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69af98a0ce708190a89b68e8e9053f43 completed March 10, 2026, 4:05 a.m.
Created at: March 4, 2026, 7:51 p.m.