Triple
T4016341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Rutskoy |
E90770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet Air Force officer |
C449
|
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 Air Force officer Context triple: [Alexander Rutskoy, instanceOf, Soviet Air Force officer]
-
A.
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.
-
B.
military officer
chosen
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
C.
Soviet scientist
A Soviet scientist is a researcher or engineer who conducted scientific or technological work within the political, ideological, and institutional framework of the Soviet Union.
-
D.
Waffen-SS officer
A Waffen-SS officer was a commissioned leader within Nazi Germany’s Waffen-SS, responsible for commanding combat units of this paramilitary organization that was deeply involved in war crimes and atrocities during World War II.
-
E.
formation of the Soviet Air Forces
The formation of the Soviet Air Forces refers to the early 20th-century process by which the Soviet state organized, structured, and expanded its military aviation arm from scattered revolutionary air units into a centralized, doctrinally unified air force.
- 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:35 p.m.