Triple
T32032148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polikarpov Design Bureau |
E817994
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet design organization |
C10693
|
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 design organization Context triple: [Polikarpov Design Bureau, instanceOf, Soviet design organization]
-
A.
Soviet design bureau
chosen
A Soviet design bureau was a state-controlled, specialized engineering and research organization responsible for conceiving, developing, and prototyping advanced military and industrial technologies within the centrally planned Soviet system.
-
B.
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.
-
C.
rocket design bureau
A rocket design bureau is an organization that specializes in the research, engineering, and development of rocket systems and related aerospace technologies.
-
D.
directorate of the Ministry of Defense of the USSR
A directorate of the Ministry of Defense of the USSR was a specialized administrative and command body responsible for managing a specific functional area of military policy, operations, or support within the Soviet armed forces.
-
E.
Soviet technology
Soviet technology encompasses the industrial, military, and scientific tools, systems, and innovations developed in the USSR, often characterized by rugged simplicity, mass production, and strategic focus over consumer comfort.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:18 a.m.