5.3× Participial clause rate GPT-4o vs human 61% Detector false-positive non-native English 95.8% Random forest accuracy trained linguists, biber features HUMAN WRITING · sparse, varied GPT-4o · dense, repeating
Field Notes / AI Methodology

The comment warriors are training the thing they hate.

A Carnegie Mellon study found GPT-4o uses present participial clauses at 5.3 times the human rate. Stanford found AI detectors flag 61% of non-native English writing as AI-generated. The pattern matchers in the comments don't have these numbers.

By Mike Goetz May 2026 9 min read
Read
5.3×
Participial clause rate, GPT-4o vs human writing (Carnegie Mellon, PNAS 2025)
61%
AI-detector false-positive rate against non-native English speakers (Stanford, 2023)
95.8%
Random forest classifier accuracy when trained on Biber linguistic features

There's a study from Carnegie Mellon, published in PNAS in February 2025, that the LinkedIn comment warriors haven't read.

It found that GPT-4o uses present participial clauses at 5.3 times the human rate. The Cohen's d effect size is 0.81, which is enormous in linguistic research. Nominalizations show up at one and a half to two times the human rate. Specific words appear at frequencies that aren't subtle. Camaraderie shows up 150 times more often in AI text than in human writing. Tapestry, also 150 times. Palpable and intricate are strong tells too.

A random forest classifier built on Douglas Biber's linguistic features hits 95.8% accuracy distinguishing human from machine. That's detection done with statistical rigor. That's what trained linguists with the right methods can do.

The person in the comments scanning for em dashes is doing something different. They're pattern matching from a viral post they read three months ago, and they're wrong more often than they're right.

01

The Stanford number that should end most of these arguments

A 2023 Stanford study found AI detectors flagged 61% of essays written by non-native English speakers as AI-generated. Sixty-one percent. That's not a detection tool. That's a tool that punishes people for writing carefully in their second language.

OpenAI shut down its own detector in 2023 because the accuracy was too low to defend. The company that built the model couldn't reliably detect the model. Meanwhile, random people in your comments are convinced they have the gift.

Black students get accused at higher rates by their teachers, according to Common Sense Media research. Researchers writing in formal grant-trained English get flagged. Writers have lost contracts and had payments withheld over false positive scores. The detection layer the comment-warrior crowd relies on is fundamentally broken, and it breaks in the direction that hurts careful writers most.

The detection tools are wrong about you 61% of the time if English is your second language. The person calling you out in the comments has worse tools than that.

02

Where the legitimate critics live

I want to be careful here. There's a critic class that knows what it's doing.

A qualitative study from Heidelberg University, the University of Melbourne, and Singapore Management University analyzed 1,154 posts across 15 Reddit and Hacker News threads about AI slop in software development. They built a structured codebook covering review friction, quality degradation, and systemic forces. The developers in those threads describe being turned into unpaid prompt engineers, reviewing code that no human had ever read before submission, trying to figure out what an AI agent had done versus what it had hallucinated. That's substantive critique from people doing the work.

Dermot O'Connor sits in this category for visual content. He can name the pattern, not just deliver the verdict. He'll tell you exactly which compositional rule the AI broke, which lighting logic doesn't hold, which detail betrays the prompt. That's craft talking. That's critique that makes the work better.

The qualitative study and the working professionals aren't the problem. They have something to say.

The problem is the layer on top of them. The audience that learned three tells from a viral post and now performs detection as a personality trait. They have a profile picture and a comment history that mostly says "this is AI" on other people's work, and very little of their own.

03

The identity defense underneath

A study from the UBC Sauder School of Business, published in Computers in Human Behavior, found people react negatively to AI art partly because it threatens what they think makes them human. That's not craft critique. That's identity defense. Different category of objection entirely, and worth naming, because mixing it up with quality assessment muddies the conversation.

Some of the loudest voices aren't really arguing about whether the work is good. They're arguing about whether the work is allowed to exist. Those are different posts.

04

The feedback loop nobody talks about

Here's what almost nobody in this debate has noticed.

When someone uses AI with methodology, brings critique back into the loop, and adjusts, the work gets better. I do this constantly with my federal contracting work. Five or six Reddit comments a day, take the feedback, feed it back into the system, build it into framework. That loop is where the Human Touch Restoration Protocol came from. People telling me what felt wrong became signal. The signal became patterns. The patterns became a seven-stage protocol that detects 95.8% of AI artifacts before content ships.

The critics didn't know they were collaborating. They thought they were policing.

If you hate AI slop and you spend your time pointing it out in the comments, you are training data for the next iteration.

If you hate AI slop and you spend your time pointing it out in the comments, congratulations. You are training data for the next iteration. The methodology people are reading what gets called out and adjusting. The actual slop generators don't read comments. They never did. The pile gets higher whether you yell at it or not.

The Sorting Principle

There's a clean way to sort this that solves most of the confusion.

Signal · listen to these

Critics with craft knowledge. Naming patterns instead of delivering verdicts. The Heidelberg researchers, the Dermot O'Connors, the developers describing review burden in production codebases. They make the work better whether the writer used AI or not. Steal their critiques and build them into your process.

Noise · ignore these

Performance critics. Scanning for em dashes and casting verdicts from viral pattern lists. Wrong about non-native English speakers 61% of the time. Wrong about Black students at elevated rates. They make innocent humans prove their humanity to strangers in comment sections, and they have no idea their tools don't work.

The tell

The first group is doing critique. The second group is doing identity work disguised as critique.

05

What this means for anyone building with AI

If you're using AI to produce work that ships, the comment warriors aren't your enemy. They're an unreliable feedback system, but they're still feedback. Read the legitimate critiques and steal them. Ignore the pattern matchers. Run your output through a detection protocol that measures structural fingerprints, not vibes.

The Human Touch Restoration Protocol exists because I got tired of the random verdict layer and built something measurable. Seven stages. Detection, deep analysis, restoration, verification. Participial clause density under 1.0 per 100 words. Nominalization density under 3.0 per 100 words. Zero AI signature vocabulary. Sentence length standard deviation above six words per paragraph. Quantifiable metrics. Benchmarks against known human-written samples.

That's the response to AI slop. Not yelling about it.

The response to AI slop is methodology, not commentary.

06

One last thing

If you're reading this and you write online and you've been falsely accused of AI authorship, especially if English is your second language, you aren't crazy and you aren't alone. The Stanford 61% number holds up. The detection tools are broken. The accusers are mostly running on pattern recognition from sources that don't work.

Keep writing. Keep version control on. Document your process. The methodology people building work that ships will recognize you faster than the comment warriors ever will, because we know what the structural fingerprints look like, and the people calling you out don't.

The work is the answer. It always was.

Want methodology, not commentary?

Framework methodology for systematic AI work, including the Human Touch Restoration Protocol behind the structural-fingerprint approach, lives at HowToFramework.

Visit HowToFramework.com

Sources Cited

  • Carnegie Mellon University, PNAS (February 2025), participial clause and nominalization analysis of GPT-4o
  • Liang et al., Stanford University (2023), AI detector bias against non-native English speakers
  • Baltes, Cheong, Treude (Heidelberg, Melbourne, Singapore Management), qualitative study of 1,154 AI slop posts
  • UBC Sauder School of Business, Computers in Human Behavior (June 2023), psychology of AI art rejection
  • Common Sense Media report on AI accusation rates by demographic
  • OpenAI classifier discontinuation announcement, 2023
  • University College Cork stylometry study (January 2025), AI vs human writing variation
MG
Mike Goetz

Mike Goetz is the founder of RageDesigner, where he has built systematic thinking methodology since 2003. His framework library now exceeds 700 documented frameworks across federal contracting, AI strategy, content production, sales, and crisis response. The Human Touch Restoration Protocol referenced above is one of those frameworks. He teaches framework generation at whatisaframework.com and howtoframework.com.