Triple
T32979223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komuch |
E843751
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-Bolshevik provisional government |
C22493
|
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: anti-Bolshevik provisional government Context triple: [Komuch, instanceOf, anti-Bolshevik provisional government]
-
A.
anti-Bolshevik government
chosen
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.
-
B.
Provisional government
A provisional government is a temporary governing authority established to manage a state during a transitional period, typically following the collapse of a previous regime or before the creation of a permanent political system.
-
C.
anti-Bolshevik military coalition
An anti-Bolshevik military coalition is a temporary alliance of armed forces and political groups united to oppose, contain, or overthrow Bolshevik or communist regimes, typically during revolutionary or civil war contexts.
-
D.
anti-Bolshevik organization
An anti-Bolshevik organization is a group formed to oppose Bolshevik ideology, policies, or rule, typically through political, military, or propaganda activities.
-
E.
anti-Bolshevik political organization
An anti-Bolshevik political organization is a group formed to oppose Bolshevik ideology and governance, typically advocating alternative political, economic, or social systems and often engaging in propaganda, activism, or coordinated resistance.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.