Triple
T31384869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary government of Georgia |
E800567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bolshevik regime |
C955
|
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 regime Context triple: [Revolutionary government of Georgia, instanceOf, Bolshevik regime]
-
A.
communist regime
chosen
A communist regime is a political system in which a single party claiming to represent the working class controls the state, economy, and major social institutions in pursuit of a classless, stateless society, typically through centralized planning and limited political freedoms.
-
B.
Stalinist
A Stalinist is someone who adheres to or advocates the authoritarian, centralized, and often repressive political practices and ideology associated with Joseph Stalin’s rule in the Soviet Union.
-
C.
anti-Bolshevik government
An anti-Bolshevik government is a political authority formed in opposition to Bolshevik rule, typically seeking to resist, overturn, or prevent the establishment of a Bolshevik-led socialist or communist regime.
-
D.
socialist republic
A socialist republic is a state governed as a republic in which political power and key means of production are formally organized and managed according to socialist principles, typically emphasizing public ownership, economic planning, and social welfare.
-
E.
soviet
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.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.