The Defence and Evacuation of the Kuban Bridgehead, \nJanuary – October 1943
Bibliographic record
Abstract
This thesis examines German and Soviet operations in the Kuban area of southern Russia\nduring January – October 1943. As the bulk of German Army Group A withdrew from the\nCaucasus in early 1943 to avoid encirclement following the Soviet counter-offensive at\nStalingrad, Seventeenth Army was ordered to hold a bridgehead on the Kuban Peninsula as\na jumping-off point for a future resumption of the German offensive into the Caucasus.\nIn early February, the Soviets attempted to eliminate the German bridgehead through a\ncombined amphibious and ground operation. The ground operation did not achieve any\nsignificant gain, and the main amphibious landing operation was a catastrophic failure, but a\nsecondary landing succeeded in gaining a foothold in the southern suburbs of the port city of\nNovorossiysk that was quickly expanded and became known as Malaya Zemlya (The Small\nLand).\nEarly April saw the launch of Operation Neptune, a German effort to eliminate the Malaya\nZemlya beachhead. This failed utterly due to the weakness of the German assault groups\nand the tenacious Soviet defence. The Soviets then launched a series of attempts through\nthe spring and summer to break the German line, with minimal success. The final phase of\noperations in the Kuban was the withdrawal of Seventeenth Army by sea and air across the\nKerch Strait to the Crimea. Almost a quarter of a million men and the bulk of their equipment\nwere successfully evacuated, with very light losses.\nThe thesis examines some factors that contributed to the success or failure of these\noperations and also considers why a region that was of key strategic interest in both German\nand Soviet planning in the first period of the war quickly diminished in importance and has\nbeen largely neglected in the published history of the war.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.006 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".