Triple
T2299221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Soviet of the Russian SFSR |
E51690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supreme soviet |
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: supreme soviet Context triple: [Supreme Soviet of the Russian SFSR, instanceOf, supreme soviet]
-
A.
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.
-
B.
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.
-
C.
policy of the Soviet Union
The policy of the Soviet Union encompasses the ideological, political, economic, and foreign strategies implemented by the Soviet state to build and maintain a socialist system under one-party rule from 1917 to 1991.
-
D.
constituent republic of the Soviet Union
A constituent republic of the Soviet Union was a nominally sovereign national republic that, while having its own government and constitution, was politically and economically subordinate to the central Soviet federal authority.
-
E.
politburo
A politburo is the principal policymaking and executive committee of a communist party, typically composed of its top leadership.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
Created at: March 4, 2026, 7:49 p.m.