Triple
T21508957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | state budget of the USSR |
E530666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | centralized financial plan |
C1641
|
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: centralized financial plan Context triple: [state budget of the USSR, instanceOf, centralized financial plan]
-
A.
centralized economic planning system
chosen
A centralized economic planning system is a structure in which a central authority makes decisions about the allocation of resources, production targets, and distribution of goods and services across an economy.
-
B.
planned regional monetary fund
A planned regional monetary fund is a proposed financial institution designed to pool resources from member countries within a specific region to provide monetary stability, balance-of-payments support, and coordinated economic policies.
-
C.
central government account
A central government account is a financial record or ledger maintained by a nation's primary governing authority to track, manage, and report its revenues, expenditures, assets, and liabilities.
-
D.
federal capital plan
A federal capital plan is a strategic, long-term framework that outlines the government’s priorities, timing, and funding for investments in major physical and technological assets to support national policy goals and public services.
-
E.
financial center
A financial center is a geographic area or hub where a high concentration of financial institutions, markets, and services are located, facilitating large-scale capital flows, investment, and economic activity.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:25 p.m.