Chronology of events from the defection of Taras through the defection of Thurii, 213–212
Bibliographic record
Abstract
The defection of Taras set off a string of revolts, including Metapontion, Heraclea and Thurii. Unfortunately, the sources for the Tarentine revolt contain a certain amount of confusion. Polybius' full narrative of the Tarentine revolt (8.24–34) is located in a fragmentary book and lacks reference to specific dates. Livy's fuller account (25.7.10–11.20) places the revolt after the beginning of the consular year 212 (25.3.1) and possibly before 26 April 212 (25.12.1). He also states, however, that most of his sources dated the event to 212, but some placed it in 213 (25.11.20). He later mentions that the Roman garrison commander in Taras held the citadel for five years (27.25.4), and since the city was recaptured in 209 (27.12.1–3, 27.15.4–16.9), this also suggests that the revolt fell in 213. Appian ( Hann . 35) also implies that Taras revolted in 213, placing it in the year before Tiberius Sempronius Gracchus died, which occurred in 212 (Liv. 25.16). Polybius' Book 8 covered Olympic years 141.1–141.4, which included both the consular years 214/13 and 213/12. Hannibal besieged the citadel of Taras during the winter (Polyb. 8.34.13), and he probably captured it sometime late in winter. It is possible that (a) he captured Taras in the winter of 213/12 but before the beginning of consular year (15 March) 212/11, or (b) if the Roman calendar was running about a month ahead of the solar calendar and 15 March (Roman) fell around 15 February (solar), then Taras could have fallen just after the start of the consular year 213 but still late in the winter season.
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.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.004 | 0.004 |
| Science and technology studies | 0.005 | 0.002 |
| Scholarly communication | 0.004 | 0.002 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.016 | 0.003 |
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".