Triple
T3684917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief of the Soviet Civil Defense |
E78200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military office |
C1854
|
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 military office Context triple: [Chief of the Soviet Civil Defense, instanceOf, Soviet military office]
-
A.
Soviet government ministry
A Soviet government ministry was a centralized state administrative body responsible for directing and managing a specific sector of the economy, society, or state functions under the authority of the USSR’s Communist Party leadership.
-
B.
military office
chosen
A military office is an administrative workspace within an armed forces organization where personnel manage planning, logistics, communication, and documentation to support military operations.
-
C.
Soviet design bureau
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.
-
D.
military political organ
A military political organ is an institutional body within the armed forces responsible for overseeing political education, ideological control, and party or state loyalty among military personnel.
-
E.
component of the Soviet Air Forces
A component of the Soviet Air Forces is an organizational unit, formation, or specialized element (such as a regiment, division, or support service) that collectively contributed to the operational, logistical, and strategic capabilities of the USSR’s military aviation.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:26 p.m.