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

“Word Play” in Qoheleth

2009· article· en· W2059595967 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
TopicArchaeology and Historical Studies
Canadian institutionsnot available
Fundersnot available
KeywordsPolysemyAlliterationLinguisticsSection (typography)Context (archaeology)Meaning (existential)Word (group theory)Subject (documents)HistoryComputer scienceLiteraturePsychologyArtPhilosophyRhymePoetry

Abstract

fetched live from OpenAlex

This study offers a comprehensive treatment of the subject of “word play” in the book of Qoheleth. After discussing the problematic nature of the term “word play,” and explaining my preference for the word “punning,” I examine six different types of punning found in Qoheleth. The first, focuses on alliteration, or the repeated use of consonants. The second section collects examples of assonance, or the repeated use of vowel patterns. The third section focuses on illustrations of polysemy; cases in which words bear more than one meaning in a single context. The fourth section, which is related to polysemy, details cases of antanaclasis. Antanaclasis occurs when a word is used multiple times, but with different meanings. In the fifth section, I provide examples of allusive punning, i.e., the use of words or forms that imply by way of similarity of sound another word that does not occur in the text. The sixth section is devoted to instances of numerical punning. After providing the data for each of these devices, I offer some general observations on punning in Qoheleth.

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: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.534
Threshold uncertainty score0.714

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.000
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.026
GPT teacher head0.238
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