Triple
T29439249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Byelorussian Congress of Soviets |
E746665
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | soviet congress |
C8127
|
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: soviet congress Context triple: [All-Byelorussian Congress of Soviets, instanceOf, soviet congress]
-
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.
soviet
chosen
Soviet refers to anything related to the former Soviet Union (USSR), including its government, ideology, culture, or people associated with its socialist, one-party state system.
-
C.
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.
-
D.
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.
-
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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:20 p.m.