MétaCan
Menu
Back to cohort
Record W2316765390 · doi:10.18647/2925/jjs-2010

A Brief History of the Second Temple Period Name ‘Hyrcanus’

2010· article· en· W2316765390 on OpenAlex
Daniel A. Machiela

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueJournal of Jewish Studies · 2010
Typearticle
Languageen
FieldArts and Humanities
TopicBiblical Studies and Interpretation
Canadian institutionsMcMaster University
Fundersnot available
KeywordsAncient historyPeriod (music)Second Temple periodTempleHistoryArtArchaeologyAesthetics

Abstract

fetched live from OpenAlex

The late Israelite / early Jewish name ‘Hyrcanus’ has proven an enigma to ancient and modern historians of Judaism, especially in terms of its etymology. With the introduction of a possible Aramaic occurence of the name among the Dead Sea Genesis Apocryphon, ‘Hyrcanus’ is now beset by further complications; some scholars suggesting that the Aramaic form is altogether different than the Greek name, while others assume a direct correspondence. Drawing on a wide array of etymological and historical data, this essay seeks to lay out clearly the various problems and previously proposed solutions in the debate over the name, examining the strengths and weaknesses of each. The result of the study is a new thesis that groups all of the name’s variant morphologies under a single, Egyptian theophore, and thereby sheds light on its employment in Judaism—especially in connection with the Hasmonean dynasty.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.145
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.001
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.000

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.

Opus teacher head0.046
GPT teacher head0.258
Teacher spread0.212 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it