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.
Bibliographic record
Abstract
After David had freed Israelite soil from the Philistine menace, he was able to move the Ark to a more appropriate place from Abinadab's dwelling. He wanted it in Jerusalem, his new capital, where he needed a focal point for the Yahwistic portion of his subjects in order to counterbalance the Jebusite symbols of the city. Some of the priests who had been associated with the Ark throughout the generations had misgivings. Not that the Ark had to go back to Shiloh but neither did they want it sequestered in Jerusalem and become part of the local cult there. So during David's triumphal progress, when they came to a place, which was acceptable according to Israelite theology of the time, the guardians of the Ark tried to retain it there. It is not certain what happened next, because each sentence of the various passages is obscure in its structure and wording, but the chief of the priestly contingent dies. Eventually this occurrence gets to be interpreted as divine intervention in favour of David's scheme. Initially though, the incident does upset David enough for him to abandon his plans. He deposits the sacred object in the first house that he comes to, and it is only after he receives assurances from the remainder of the population, that he resumes his first ambition and he brings the Ark into Jerusalem . The name of the place though, Perez-uzzah, remains a constant reminder to David that a break had been made in his strength, his, David's, power. David was never able to overcome this breach, and neither was his son Solomon.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.003 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it