The Mound on the Mount: A Possible Solution to the Problem with Jerusalem
Bibliographic record
Abstract
Following Knauf's suggestion (2000), the article raises the possibility that in most periods in the second and first millennia BCE the main built-up area of Jerusalem was limited to a mound on the Temple Mount. This mound, which may have covered an area of five hectares and more, was boxed-in under the Herodian platform. At these periods activity in the City of David ridge was restricted to the area near the Gihon spring. In the Iron IIB and late Hellenistic Periods the fortified settlement expanded simultaneously to both the City of David ridge and the southwestern hill. In these two periods there was no need to fortify the western side of the City of David, as this line ran in the middle of the city.
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.002 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.009 | 0.011 |
| Scholarly communication | 0.005 | 0.004 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.003 | 0.004 |
| Insufficient payload (model declined to judge) | 0.010 | 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".