Triple
T8836892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolshevik Party program |
E210287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian political document |
C13140
|
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: Russian political document Context triple: [Bolshevik Party program, instanceOf, Russian political document]
-
A.
Soviet document
chosen
A Soviet document is an official or unofficial written record produced within the Soviet Union’s political, administrative, or social systems, reflecting its bureaucratic procedures, ideology, and historical context.
-
B.
Soviet government position
A Soviet government position is an official role within the political and administrative hierarchy of the USSR, responsible for implementing Communist Party policies and managing state functions at various levels.
-
C.
Russian newspaper
A Russian newspaper is a periodical publication, printed or digital, produced in the Russian language (or within Russia) that reports news, commentary, and other information relevant to Russian-speaking audiences.
-
D.
Russian state
The Russian state is a centralized political entity that exercises sovereign authority over the territory and population of Russia through its institutions of governance, law, security, and administration.
-
E.
post–Cold War settlement document
A post–Cold War settlement document is a formal agreement or framework, typically involving states and international organizations, that redefines political, security, and economic arrangements in the aftermath of the Cold War’s bipolar order.
- 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_69ca8388549c819095fd94eadefbb007 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:47 p.m.