Triple

T2218224
Position Surface form Disambiguated ID Type / Status
Subject Zemsky Sobor of 1613 E48080 entity
Predicate instanceOf P0 FINISHED
Object Zemsky Sobor C8323 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: Zemsky Sobor
Context triple: [Zemsky Sobor of 1613, instanceOf, Zemsky Sobor]
  • A. 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.
  • B. revolutionary congress
    A revolutionary congress is a formal assembly of representatives convened to lead, coordinate, and legitimize a political or social revolution, often drafting new governing frameworks and strategies for transformative change.
  • C. election in the Soviet Union
    An election in the Soviet Union was a state-controlled political process in which candidates, typically preselected by the Communist Party, were formally approved by voters in largely non-competitive, single-party ballots.
  • D. Grand Prince of Moscow
    The Grand Prince of Moscow was the medieval ruler of the Grand Duchy of Moscow, who gradually consolidated Russian lands, led resistance against foreign domination, and laid the foundations for a centralized Russian state.
  • E. plebiscite
    A plebiscite is a direct vote by the entire electorate on a specific proposal or issue, allowing citizens to decide a public question rather than elected representatives.
  • F. None of above. chosen

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_69a88aa1ee708190862c8c378c41e9eb completed March 4, 2026, 7:40 p.m.
Created at: March 4, 2026, 7:46 p.m.