Triple
T10108505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Party Unity |
E218182
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bolshevik Party resolution |
C5378
|
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: Bolshevik Party resolution Context triple: [On Party Unity, instanceOf, Bolshevik Party resolution]
-
A.
supreme soviet
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.
-
B.
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.
-
C.
politburo
chosen
A politburo is the principal policymaking and executive committee of a communist party, typically composed of its top leadership.
-
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.
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.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.