Triple

T23406033
Position Surface form Disambiguated ID Type / Status
Subject Soviet Union E559936 entity
Predicate capital P234 FINISHED
Object Moscow, Russian SFSR NE NERFINISHED

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: Moscow, Russian SFSR | Statement: [Soviet Union, capital, Moscow, Russian SFSR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moscow, Russian SFSR
Context triple: [Soviet Union, capital, Moscow, Russian SFSR]
  • A. Moscow, Soviet Union chosen
    Moscow, Soviet Union was the capital and largest city of the Soviet Union, serving as its political, economic, and cultural center.
  • B. Moscow
    Moscow is the capital and largest city of Russia, serving as its political, economic, and cultural center.
  • C. Moscow
    Moscow is a small borough in Lackawanna County, Pennsylvania, known as a residential community near the Scranton metropolitan area.
  • D. Moscow
    Moscow is a small rural community located within the Township of Stone Mills in eastern Ontario, Canada.
  • E. Moscow
    Moscow is a fictional character from the Spanish television series "Money Heist" (La Casa de Papel), known as a kind-hearted, blue-collar miner and the father of Denver who participates in the Royal Mint heist.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2454b3a5881909c64773dc8a5d289 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1a4e364548190b98dc09240fba58e completed April 29, 2026, 6:27 a.m.
Created at: April 17, 2026, 5:38 p.m.