Justin on tribunates and generalships, <i>Casares</i> , and <i>Augusti</i>
Bibliographic record
Abstract
Little, if anything, in Justin scholarship has been as controversial as the dating of the so-called Epitome of the Philippic History of Pompeius Trogus . Suggested dates have varied from the time of Antoninus Pius through the third century to the end of the fourth. The latter was proposed in 1988 by Sir Ronald Syme, but has in fact received little support in subsequent literature on Justin, which has tended to accept the earlier dating (late second/early third centuries). An exception is T. D. Barnes, who has voiced support for a later dating based on a linguistic parallel to Justin in the Historia Augusta . Barnes observes that Oscar Hey, author of the article ducatus in TLL (5.2129.30–2131.42), drew attention to the similarity between Justin 30.2.5 Agathocles regis lateri iunctus civitatem regebat, tribunatus et praefecturas et ducatus mulieres ordinabant and HA Heliog . 6.2 militaribus… praeposituris et legationibus et ducatibus venditis . Hey, he notes, refers at the head of that particular section of the article (Section 2 [2130.5–63]) to Seeck's article on dux. Seeck had demonstrated—and this is now taken for granted by scholars—that from the time of Diocletian dux is used technically as a formal title, and, in drawing attention to the parallel between HA Heliog . 6.2 and Justin, Hey must have been intimating that Justin is, like the author of Heliog . 6.2, using ducatus as a (post-Diocletianic) formal title. He then seems to suggest that Hey was right and Justin is to be dated to at least some time after 260.
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.001 | 0.001 |
| Science and technology studies | 0.005 | 0.006 |
| Scholarly communication | 0.005 | 0.003 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.008 | 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".