Triple

T33964002
Position Surface form Disambiguated ID Type / Status
Subject Fifth All-Russian Congress of Soviets E870799 entity
Predicate instanceOf P0 FINISHED
Object All-Russian Congress of Soviets C9531 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: All-Russian Congress of Soviets
Context triple: [Fifth All-Russian Congress of Soviets, instanceOf, All-Russian Congress of Soviets]
  • A. Zemsky Sobor
    Zemsky Sobor was a representative assembly in 16th–17th century Russia, convened by the tsar to consult nobles, clergy, and other estates on major state matters such as succession, legislation, and foreign policy.
  • B. supreme soviet chosen
    The Supreme Soviet was the highest legislative body in the Soviet Union (and in its constituent republics), formally empowered to enact laws, approve plans and budgets, and elect key state officials, though in practice it largely ratified decisions made by the Communist Party leadership.
  • C. Communist Party of Russia resolution
    A Communist Party of Russia resolution is a formal, collectively adopted document that outlines the party’s official position, decisions, or directives on specific political, ideological, or organizational issues within the Russian context.
  • D. Soviet election
    A Soviet election was a state-controlled, non-competitive electoral process in the USSR, typically featuring a single approved candidate per seat and serving primarily to legitimize Communist Party rule rather than to offer genuine voter choice.
  • E. Cossack communal assembly
    A Cossack communal assembly is a self-governing gathering of Cossack community members that collectively deliberates and decides on political, military, and social matters.
  • F. None of above.

Provenance (1 batch)

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_69f3499ce8e88190b66e1d49ad8c7037 completed April 30, 2026, 12:22 p.m.
Created at: May 1, 2026, 1:50 a.m.