Bibliographic record
Abstract
Immediately following the capture of Consentia and Petelia, Carthaginian forces moved against the Greek cities of Bruttium, attacking first Rhegion then Locri. Polybius records that the siege of Petelia lasted eleven months, and this date is followed by Frontinus, while Livy mentions only an unspecified number of months. Walbank (1970: II.30–1) argues that the siege would have ended late in the summer of 215, perhaps in September, assuming (1) a couple of months passed from the battle at Cannae until the investment of Petelia, and (2) the Roman calendar was in line with the solar calendar. This position is difficult to reconcile with Livy's claim that Carthaginian forces landed at Locri, which fell after Petelia, then marched to Hannibal in Campania and finally returned to Bruttium by the end of the campaign season. If Locri fell a few weeks after Petelia, then the reinforcements could not have arrived until late September or early October. Hanno would not have reached Hannibal with the reinforcements until mid- or late October, and he would not have returned to Bruttium until (probably) sometime in November. Even if the Roman calendar were running well ahead of the seasons, by a month or even six weeks (Derow 1976), then Hanno would have returned to Bruttium in October, still very late in the campaign season. It is unlikely, though not impossible, that the Carthaginians conducted operations so late in the year.
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.007 | 0.007 |
| Science and technology studies | 0.003 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.000 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.019 | 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".