THE CRIMINAL CHARGES AGAINST AGRIPPINA THE ELDER IN <scp>a.d.</scp> 27 AND 29
Bibliographic record
Abstract
Tacitus traces a series of conflicts between Agrippina the Elder and her father-in-law Tiberius. After the death of her husband Germanicus in Syria (a.d. 19), Agrippina returned to Rome with their children. Germanicus' lingering popularity with the armies and people meant that his widow Agrippina and their children enjoyed a level of popular support as well—one that eventually became a threat in Tiberius' mind. Agrippina, moreover, refused to embrace the modest, retiring role that her father-in-law (and Roman society in general) expected of her. Tiberius was, moreover, ‘never gentle toward the house of Germanicus’ and his concerns were augmented by the machinations of Sejanus, who reported that the people were dividing themselves into factions, some even calling themselves members of the partes Agrippinae. The combination of Agrippina's high birth—the only still-living grandchild of Augustus—and her status as widowed daughter-in-law of the emperor, therefore mother of the emperor's probable heir, along with her persistent independence and sometimes unfeminine strength of character made her seem an intolerable political threat. This paper examines the culmination of these conflicts, when Agrippina is subjected to criminal prosecution and penalty in a.d. 27 and 29 at the instigation of Sejanus, with the overt approval of Tiberius. Of primary concern is the timing and the order of the charges brought against Agrippina.
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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.009 | 0.002 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.005 | 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".