Triple
T2580142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decree on Land |
E57069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet land reform measure |
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 land reform measure Context triple: [Decree on Land, instanceOf, Soviet land reform measure]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:49 p.m.