Triple

T2791592
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Moscow (1970) E61940 entity
Predicate party P1790 FINISHED
Object USSR E363 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: USSR | Statement: [Treaty of Moscow (1970), party, USSR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: USSR
Context triple: [Treaty of Moscow (1970), party, USSR]
  • A. Soviet Union chosen
    The Soviet Union was a socialist superpower that dominated Eastern Europe and led the communist bloc during the Cold War.
  • B. Russian SFSR
    The Russian SFSR was the largest and most influential republic of the former Soviet Union, encompassing much of its political, economic, and cultural center.
  • C. MO USSR
    MO USSR was the central government body responsible for directing and coordinating the armed forces of the Soviet Union.
  • D. Soviets
    Soviets were grassroots councils of workers, soldiers, and peasants that emerged as powerful political organs during the Russian Revolution and became a foundational element of the Soviet state.
  • E. Soviet Socialist Republics
    The Soviet Socialist Republics were the constituent republic-level units of the Soviet Union, each nominally sovereign but centrally controlled by the communist government in Moscow.
  • 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_69ab4b7f51d881908768300ebd2fbdae completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abddcfe19c81908f94dd449f18a2c2 completed March 7, 2026, 8:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69bdacb883188190a213986b2816cde2 completed March 20, 2026, 8:23 p.m.
Created at: March 6, 2026, 9:58 p.m.