Triple
T20933467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Latinization campaign |
E515524
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet policy initiative |
C1642
|
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 policy initiative Context triple: [Soviet Latinization campaign, instanceOf, Soviet policy initiative]
-
A.
policy of the Soviet Union
chosen
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.
-
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.
Soviet economic policy
Soviet economic policy refers to the centrally planned, state-controlled system that directed production, distribution, and investment according to government-determined goals rather than market forces, aiming to rapidly industrialize and achieve socialist objectives.
-
D.
Maoist policy initiative
A Maoist policy initiative is a government or party-driven program designed to implement Mao Zedong’s principles of class struggle, mass mobilization, and collectivist economic and social transformation.
-
E.
Soviet organization
A Soviet organization is an institution, agency, or collective entity established under the governance and ideological framework of the Soviet Union to manage political, economic, social, or military functions.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:49 p.m.