Triple
T13086140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet military–industrial complex |
E310341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-controlled industrial system |
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: state-controlled industrial system Context triple: [Soviet military–industrial complex, instanceOf, state-controlled industrial system]
-
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.
industrial production system
An industrial production system is an organized arrangement of people, machines, materials, methods, and information designed to efficiently transform inputs into standardized goods or services at scale.
-
C.
state-controlled labor organization
A state-controlled labor organization is a government-dominated entity that formally represents workers but primarily serves state and ruling-party interests in regulating labor relations, often limiting independent worker advocacy and collective bargaining.
-
D.
central control system
A central control system is a coordinating entity that monitors, manages, and directs the operations of interconnected components or subsystems to achieve overall system objectives.
-
E.
state-owned railroad
A state-owned railroad is a railway system owned and operated by a government entity, providing rail transport services as a public enterprise.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
Created at: April 9, 2026, 9:02 p.m.