Skip to content
Read • Question • ConnectAnthony’s notes & researchReturn with a new question
Anthony’s NotesA personal field guide
From the notebook

Search Terms and Their Allegations

Every count in the book set beside the claim attached to it, sorted by whether a frequency can carry that claim.

Every quantitative finding in the book, paired with the interpretive claim attached to it, and an assessment of whether the counting method can support that claim.

The recurring pattern: the measurement is a frequency, and the claim attached is frequently a universal — all, virtually all, almost always, every time. A frequency count establishes how often a string appeared. It cannot establish what every instance meant. Where a universal is asserted, hand-coding of every instance would be required, and no such coding is reported.

What the counts include

The book states its counting rule once, parenthetically, at Attachment (file not included in this release):

(Note: this count is conservative in that it does not include quotes from US and Israeli officials or outside commentators. The count is only the terms being used outside of quotes—it is editorial language used in ostensibly straight factual reporting.)

This matters more than its placement suggests, and it cuts both ways. It is a genuinely conservative choice that strengthens the emotive-terms findings: editorial voice is the thing an editor controls, so restricting to it isolates the editorial decision. It is also the reason the near-zero Palestinian counts may not mean what an unattributed replication would suggest, since a query that cannot distinguish quoted from editorial usage is measuring a different quantity. That is the unresolved question in 04 - Results Stage 1.

Note also that the rule is stated for the Chapter 2 emotive-terms analysis specifically. Whether it was applied to the later counts in this table is not stated anywhere.

The table

Search termOutletsTime periodResultAttached claimCan the count support it?Book
massacre, barbaric, savage, slaughterAP, CNN.com, Politico, USA Today, NYT, WaPo, AxiosFirst 100 days494:1 (Israeli:Palestinian)Atrocity language reserved for Israeli victimsPartly. Count sound; vulnerable to event-form objectionAttachment (file not included in this release)
massacre, barbaric, savage, slaughterCNN, MSNBCFirst 30 days721:30 (MSNBC 348:12, CNN 373:18)SamePartly. Same caveat. Corrected 2026-08-04: this row previously read 1,053:43, a figure that appears nowhere in the bookAttachment (file not included in this release)
“human shield(s)“NYT, WaPo, Politico, AxiosFirst year231:5 (5 all WaPo)Allegation applied to one party, withheld for other despite comparable documentationYes. Same allegation, same vocabulary, same evidentiary basis available. Strongest finding in the bookAttachment (file not included in this release)
“human shield(s)“CNN, MSNBCFirst year888:0 (CNN 438, MSNBC 450)SameYes. Same reasoningAttachment (file not included in this release)
“Hamas-run” / “Hamas-controlled”CNN, MSNBCFirst 100 daysCNN 277, MSNBC 146; zero before Oct 17Doubt-sowing qualifier adopted as policy after al-AhliYes. Evidence is the before/after discontinuity, not the total. Corroborated by CNN standards memo reported by the InterceptAttachment (file not included in this release)
“right to defend itself”CNN, MSNBCSurvey period (unstated)755:8Typically followed by rationalization of mass civilian killingNo. Claim about what the phrase does in a sentence; function never countedAttachment (file not included in this release)
“right to defend itself”Print outletsFirst year459:4SameNo. Same problemAttachment (file not included in this release)
“civilization”CNN, MSNBCSurvey period (unstated)150 mentionsAll 150 referred to Israeli/American culture, all contrasted with alleged Palestinian barbarityNo. Double universal over 150 instances; no coding reportedAttachment (file not included in this release)
“barbaric”, “savage”Print outletsFirst 100 days14:0 and 16:0Terms carry colonial-racial connotation, deployed to dehumanizeNo. Etymological argument, possibly correct; frequency cannot demonstrate connotation or intentAttachment (file not included in this release)
“hostage” vs “prisoner”CNN, MSNBCOne year46,585 vs 3,947Virtually all hostage uses Israeli, virtually all prisoner uses PalestinianNo. “Virtually all” over 46,585 instances is unverified and unverifiable without samplingAttachment (file not included in this release)
“hostage”/“kidnapped” vs “prisoner”/“detain”7 print outletsOne year30,237 vs 6,420SameNo. Same problem; also non-commensurable categoriesAttachment (file not included in this release)
“Hamas stronghold” and variantsNYTOct 2023 – Oct 2024154 usesAlmost always deployed while reporting war crimes or pending war crimesNo. Five headline examples given; five instances do not establish a pattern across 154Attachment (file not included in this release)
“Israeli hostages” vs “Palestinian prisoners”Sunday showsOct 7 2023 – Oct 7 2024835 vs 52Every prisoner mention was in exchange context onlyNo. Universal over 52 instances, not reported as checked; also non-substitutable legal categoriesAttachment (file not included in this release)
“right to defend itself”Sunday showsOct 7 2023 – Oct 7 2024149, all for IsraelPalestinians never granted the rightPartly. Zero is checkable; but see commensurability problemAttachment (file not included in this release)
“Hamas-run”Sunday showsOct 7 2023 – Oct 7 202431 usesPalestinian deaths hedged, Israeli deaths stated as factYes. Asymmetric sourcing convention is directly observableAttachment (file not included in this release)
antisemitism vs IslamophobiaSunday showsOct 7 2023 – Oct 7 202465 vs 4Asymmetric concern for bigotryPartly. Commensurable, but no control for news events driving eachAttachment (file not included in this release)
massacre, barbaric, savage, slaughterMorning Joe (MSNBC)First 6 months81:0, 22:0, 38:0, 119:1Most aggressively anti-Palestinian program on cable newsPartly. Not Johnson’s data — cites Marcetic’s Jacobin study; inherits its method unexaminedAttachment (file not included in this release)
Civilian mentions, Ukraine vs GazaCNN, MSNBCFirst 100 days of each29,534 vs 15,062 (CNN 15,593 vs 7,569)Twice the coverage despite five times the death tollQualified. Matched windows, same networks, victim group varied — the best design in the book. But the term list is not what the claim says it is, and correcting for that takes 1.96x to 1.40x. See 09 - The Civilians Query ProblemAttachment (file not included in this release)
Refugee/displacement terms, Ukraine vs GazaCNN, MSNBCFirst 100 days of each1,663 vs 211Eight times more humanizing language despite greater displacementYes. Same matched designAttachment (file not included in this release)
Child victims, Ukraine vs GazaCNN, MSNBCFirst 100 days of each4,223 vs 3,632Asymmetric attention to childrenPartly. Gap is narrow relative to the claimed disparityAttachment (file not included in this release)
“genocide”/“war crime”, Ukraine vs GazaCNN, MSNBCFirst 30 days of each17.2x for UkraineAsymmetric willingness to name atrocityUnresolved. Gaza query string records “genoicde” misspelledAttachment (file not included in this release)

The pattern, stated plainly

Sorting the rows, three groups emerge.

Findings where the number is the argument. Human shields, “Hamas-run,” and the Ukraine comparisons. In each case the count directly instantiates the claim: the same term, available to both parties, applied to one. Nothing interpretive has to be added. These survive scrutiny.

Findings where a universal has been bolted onto a frequency. “Civilization” all 150 times, “hostage” virtually all 46,585, “Hamas stronghold” almost always, “Palestinian prisoners” every time. Here the number is real and the claim is a separate assertion that the number does not test. Some may well be true — a hand-coded sample could establish them — but as published they are unsupported.

Findings where the claim is about connotation or function. Barbaric and savage as colonial vocabulary; “right to defend itself” as a rationalization device. These are literary and rhetorical arguments. They may be persuasive on their own terms. Frequency data neither supports nor refutes them, and presenting a count alongside them implies an evidentiary basis that is not there.

Why this matters more than the arithmetic

The discrepancies in 05 - Findings Register are minor and mostly run against the book’s own case. This is the more serious methodological problem, and it is systematic rather than incidental.

The rhetorical structure repeats: state a count, then state a universal, then let the count’s specificity lend authority to the universal. A reader who checks the number finds it accurate, and reasonably infers the sentence around it was checked too. It was not.

What this does and does not establish

That a claim is unsupported by the cited evidence does not make it false. Several of these universals are plausible on their face and would likely survive a coding pass. The finding here is about the gap between what was measured and what was asserted — which matters especially for a book that explicitly claims to prove its case beyond a reasonable doubt.

Checkable next

The universals are the most tractable remaining work, because most are small enough to verify exhaustively:

  1. “Palestinian prisoners” on the Sunday shows — 52 instances, all retrievable via GDELT clip export. Code each for whether it appears in an exchange context. Fully settles that claim. Book: Attachment (file not included in this release)
  2. “Civilization” — 150 instances. Code each for referent and contrast. Book: Attachment (file not included in this release)
  3. “Hamas stronghold” — 154 NYT uses. Code each for whether it accompanies war-crime reporting. Book: Attachment (file not included in this release)
  4. “Hostage”/“prisoner” — too large to code exhaustively. Draw a random sample of 200 per term and estimate the “virtually all” rate with a confidence interval.

Each of these either substantiates Johnson’s claim or does not, and each is a day’s work at most.