MétaCan
Menu
Back to cohort
Record W1996185373 · doi:10.5508/jhs.2007.v7.a13

Crime Scene Investigation: A Text-Critical Mystery and the Strange Death of Ishbosheth

2009· article· en· W1996185373 on OpenAlex

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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of Hebrew Scriptures · 2009
Typearticle
Languageen
FieldArts and Humanities
TopicBiblical Studies and Interpretation
Canadian institutionsnot available
Fundersnot available
KeywordsWitnessReignHebrewSubject (documents)Key (lock)LiteraturePhilosophyNoonHistoryArtLawLinguisticsPolitical sciencePhysicsComputer scienceAstronomyPolitics

Abstract

fetched live from OpenAlex

The troublesome reign of Ishbosheth comes to a graphic conclusion when he is assassinated – audaciously, at midday while reclining on a couch in his own house – by two of his own captains, the brothers Rechab and Baanah. That Ishbosheth is assassinated (while sleeping in his house at high noon) there is no doubt: the guilty confess, are charged, and duly executed. But the puzzle is how exactly the murder takes place – and this is subject of my analysis – as there are significant discrepancies between the Hebrew and Greek texts. This article surveys a number of “solutions” posited by scholars and evaluate various attempts that have been made to resolve this text-critical mystery. I then move toward a conclusion by summarizing the key differences between the MT and LXX in this passage and discussing some of the literary implications that emerge when these textual trajectories are compared. As a witness to the murder, the LXX provides an exciting and compelling testimony, but the MT account features several important details that cannot be ignored in light of the larger storyline.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.611
Threshold uncertainty score0.273

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.0000.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.039
GPT teacher head0.265
Teacher spread0.226 · 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