Triple
T28079745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | September 1965 plenum decisions of the CPSU Central Committee |
E709643
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | economic reform decision |
C1637
|
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: economic reform decision Context triple: [September 1965 plenum decisions of the CPSU Central Committee, instanceOf, economic reform decision]
-
A.
economic transformation
Economic transformation is the profound, structural reconfiguration of an economy’s sectors, institutions, and technologies that shifts how value is created, distributed, and sustained over time.
-
B.
economic transformation program
An economic transformation program is a coordinated set of policies and initiatives designed to fundamentally restructure and modernize an economy to achieve sustainable, inclusive growth and increased competitiveness.
-
C.
economic policy
chosen
Economic policy is a set of government decisions and actions designed to influence a nation's economic performance, including growth, employment, inflation, and income distribution.
-
D.
economic policy meeting
An economic policy meeting is a formal gathering where policymakers, experts, and stakeholders discuss, evaluate, and decide on strategies and measures to influence a region’s or nation’s economic performance.
-
E.
economic initiative
An economic initiative is a coordinated plan or program designed to stimulate economic activity, improve financial conditions, or achieve specific development goals within a market, sector, or region.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:51 p.m.