Why document-level detection breaks in real classrooms
Most deployed AI detection systems treat a submission as a single input and return a single probability estimate. This works reasonably well when the document is entirely human-written or entirely machine-generated. The problem is that this is not how students actually use LLMs.
In practice, the common pattern is partial use: a student writes most of an essay themselves, then uses ChatGPT to generate an introduction, polish a few paragraphs, or draft a literature review section. A Coursera/Censuswide survey (fieldwork October 2025, published February 2026) found that 80% of students reported AI tools improved their academic performance, while only 20% of educators reported that their university had a formal AI policy in place. The gap is not surprising. What it means for detection is that the real-world input distribution is dominated by hybrid documents, not pure-class ones.
A document-level classifier receiving a 3,000-word essay with two AI-generated paragraphs faces an awkward choice. If its aggregation function is sensitive, it flags the whole document and the educator sees “68% AI probability” with no way to locate the actual AI content. If it’s conservative, the signal from two paragraphs gets diluted and the system misses it entirely.
Liang et al. (2023) showed that seven GPT detectors misclassified TOEFL essays by non-native English speakers as AI-generated at an average rate of 61.3%, with at least one detector flagging 97.8% of those essays. Turnitin’s own documentation reports a 4% sentence-level false positive rate. At a mid-sized university processing 50,000 submissions per semester, even a 3% FPR translates to 1,500 false accusations.
What other detection approaches do
Document-Level Classifiers
Most AI detection tools operate at the document level, though several now overlay sentence-level highlighting as a post-hoc visualization step. The underlying classifiers are typically transformers trained on binary classification (human vs. machine) using perplexity, burstiness, and distributional features (Mitchell et al., 2023; Gehrmann et al., 2019). GPTZero reports detecting 95.7% of AI text at a 1% document-level false positive rate on the RAID benchmark, with accuracy exceeding 99% when filtered to modern frontier LLMs. Independent evaluations tell a different story: a 2023 evaluation of 14 detectors found that all scored below 80% accuracy and only 5 exceeded 70%, with a systematic bias toward classifying text as human-written. (Weber-Wulff et al., 2023)
Non-Native Writer Bias
Non-native writers use more predictable vocabulary, shorter sentences, and simpler syntactic constructions. Perplexity-based detectors interpret low perplexity as a machine signal, which creates a direct conflict with the linguistic profile of L2 writers. Vanderbilt disabled Turnitin’s AI detector in August 2023 specifically because of this issue.
Sentence-Level and Sequence Labeling Approaches
Emi and Spero (2024) introduced hard negative mining and synthetic mirror training for reducing false positives in a transformer-based text classifier. Lekkala et al. (2025) framed AI detection as a sentence-level segmentation task using CRF layers on top of transformer encoders. Our work is closest to Lekkala et al. but uses a simpler classification head with a sliding context window, trading global sequence dependencies for faster inference, and focuses specifically on academic use cases with attendant fairness requirements around non-native English writers.
How the system works
The classifier is built on a proprietary fine-tuned transformer encoder. For each target sentence, we construct an input sequence consisting of the two preceding sentences, a separator, the target sentence, another separator, then the two following sentences. The flanking sentences provide discourse context; the target sentence is the classification focus.
The classification head is a single linear layer over the pooled encoder representation, producing a scalar logit passed through sigmoid to yield a probability that the sentence is AI-generated, given its context. We apply temperature scaling on a held-out calibration set of 5,000 sentences to produce calibrated confidence scores. Post-calibration, a sentence scored at 0.90 is empirically AI-generated 89.4% of the time, within 1% of stated confidence across all bins above 0.5.
Training data composition
| Pool | Documents | Source | Notes |
|---|---|---|---|
| Human-authored | 82,341 | arXiv, CORE, Semantic Scholar ORC, open thesis repositories | Pre-Nov 2022 publication, 14 disciplines, ~48M sentences |
| AI-generated | 78,204 | GPT-5, Claude Sonnet 4.5, Gemini 2.5 Pro, Llama 4 Maverick, DeepSeek-R1, Mistral Large 2, Qwen 3.5*, Grok 3* | *Reserved for blind-test evaluation only |
| Mixed-authorship | 35,120 | Synthetic splicing of AI into human docs | 4 density levels × 4 position distributions |
Models selected reflect the frontier LLM landscape as of February 2026, when training data generation completed. Subsequent releases (e.g., Claude Sonnet 4.6, GPT-5.5, Grok 4) were not evaluated in this study; a 2026 refresh benchmark is planned.
Why hard negative mining matters for academic text
After initial fine-tuning, we run the model over a pool of 200k human-authored sentences held out from training. Every sentence the model classifies as AI with probability above 0.5 is extracted as a hard negative and added to the training set at a 1:3 ratio. This cycle repeats five times.
The hard negative pool is deliberately enriched with categories that produce elevated false positive rates in pilot testing: non-native English academic text (TOEFL/IELTS essay corpora, ESL thesis collections), formulaic disciplinary prose (clinical case reports, legal briefs, patent applications), and highly structured formats (methods sections, lab protocols, statistical results paragraphs). Without hard negative mining, the model treats low-perplexity, predictable prose as an AI signal regardless of authorship. The mining forces it to distinguish between “predictable because formulaic” and “predictable because machine-generated.”
For each human document, we also generate a synthetic mirror: an AI-generated text matched in topic, structure, length, and approximate register. This prevents the model from learning spurious correlations between subject matter and class labels. Emi and Spero (2024) demonstrated the effectiveness of this approach for general-domain text; we extend it to academic writing with format-aware prompting.
How we evaluated
The evaluation set is disjoint from training – no overlapping source documents or authors where attribution was available. It consists of three subsets: 4,200 fully human-authored academic texts (stratified by discipline, document length, and writer demographics, with a 10% random sample manually verified by two annotators at Cohen’s kappa = 0.94); 3,800 fully AI-generated texts from all eight LLMs including the two blind-tested models; and 2,600 mixed-authorship documents with sentence-level ground truth.
The non-native English subset (n=620) was drawn from the human-only pool and includes texts from writers whose first language spans 23 language families. We report document-level false positive rate, sentence-level precision/recall/F1 on the mixed-authorship subset, FPR disaggregated by native vs. non-native writer populations, and per-model detection accuracy. We compare against a document-level transformer classifier trained on the same data and DetectGPT applied at the sentence level. All baselines use the 0.85 confidence threshold for FPR calculation.
Document-level FPR and sentence-level performance vs. baselines
| Metric | Proofademic | Doc-level baseline | DetectGPT |
|---|---|---|---|
| Doc FPR (all) | 0.2% | 2.9% | 14.2% |
| Doc FPR (native English) | 0.6% | 1.8% | 8.1% |
| Doc FPR (non-native, n=620) | 0.6% | 1.8% | 31.6% |
| Sent. precision (mixed) | 94.1% | n/a | 72.3% |
| Sent. recall (mixed) | 91.7% | n/a | 64.8% |
| Sent. F1 (mixed) | 92.9% | n/a | 68.3% |
Hard negative mining closes the native vs. non-native FPR gap from 4.6 percentage points (document-level baseline) to 0.3 points in our system.
Detection accuracy by source LLM
| Source LLM | Detection Accuracy | Seen in training |
|---|---|---|
| GPT-5 | 99.9% | Yes |
| Claude Sonnet 4.5 | 99.8% | Yes |
| Gemini 2.5 Pro | 99.7% | Yes |
| Llama 4 Maverick | 99.4% | Yes |
| DeepSeek-R1 | 99.5% | Yes |
| Mistral Large 2 | 99.6% | Yes |
| Qwen 3.5 | 98.1% | No |
| Grok 3 | 97.6% | No |
Sentence-level F1 by AI content density
| AI Density | Precision | Recall | F1 |
|---|---|---|---|
| 10% | 91.2% | 86.4% | 88.7% |
| 25% | 93.6% | 90.8% | 92.2% |
| 50% | 95.1% | 93.5% | 94.3% |
| 75% | 96.3% | 95.8% | 96.0% |
The 10% density case is the hardest and most practically important – it represents three or four AI sentences in a 40-sentence paper. 88.7% F1 at this density means flagged sentences are enough to initiate a conversation, and 91.2% precision means flagged sentences are almost always actually AI-generated.
Ablation: context window size
| Window | Sentence F1 | Doc FPR |
|---|---|---|
| 1 (target only) | 87.4% | 3.2% |
| 3 (1+1) | 90.8% | 0.4% |
| 5 (2+2) | 92.9% | 0.2% |
| 7 (3+3) | 92.7% | 0.2% |
| 9 (4+4) | 92.4% | 0.2% |
Performance peaks at a 5-sentence window. Beyond that, wider windows start including context from different authorship zones in hybrid documents, adding noise rather than signal.
This is an internal Proofademic evaluation, not an independent third-party benchmark. Performance was measured on the specific datasets and conditions described above. Production performance will vary with document characteristics, domain, writer demographics, and adversarial paraphrasing tools not controlled for in this study. We are committed to publishing comparable head-to-head benchmarks against other commercial detection tools in future studies.
What this means in practice
The main result is that sentence-level classification with hard negative mining dramatically reduces the FPR gap between native and non-native English writers. This matters for institutional deployment. A university that processes submissions from a diverse student body cannot accept a system that disproportionately flags international students; beyond the fairness concern, it creates real legal exposure.
The sentence-level output also changes how the tool gets used in practice. When an educator sees a single document score of 68%, they face a binary decision with no supporting evidence. When they see four highlighted sentences in an otherwise clean document, they can point to specific passages and ask the student about them. This shifts the workflow from “the tool says you cheated” to “can you walk me through how you wrote these sections?” – which is closer to how academic integrity conversations should work.
Limitations
Several caveats apply to the results above. We surface them here rather than burying them in a footer.
-
Synthetic splicing, not real student work
The mixed-authorship evaluation uses programmatically spliced documents, not real student hybrid submissions. Real students edit, paraphrase, and blend AI output in ways our splicing methodology doesn't fully capture.
-
English only
We make no claims about non-English academic text.
-
No evaluation against AI humanizer tools.
Adversarial paraphrasing is a known and growing challenge. Prior work shows paraphrasing attacks can dramatically reduce detection accuracy - Krishna et al. (2023) reported DetectGPT accuracy dropping from 70.3% to 4.6% under DIPPER paraphrasing. We did not evaluate humanizer-modified text in this study.
-
Production threshold is configurable
The 0.85 confidence threshold used for FPR calculation is a production default, not a universal optimum. Institutions with different risk tolerances need different thresholds. We provide per-threshold FPR curves to institutional partners.
Conclusion
Sentence-level granularity is not just a technical improvement over document-level classification – it changes the operational model for how detection tools are used in academic settings. When the output is specific and interpretable, the tool supports evidence-based conversations instead of binary verdicts.
For institutions deploying AI detection at scale, the practical implications are concrete: dramatically lower false positive rates on non-native English writing, the ability to point to specific flagged passages instead of document-wide scores, and a workflow that fits how academic integrity conversations should actually happen. The full methodology and results are available in the research paper (PDF).
Frequently Asked Questions
Why use sentence-level detection instead of a single document score?
Document-level scores collapse a whole submission into one number, which is uninformative when the document is mixed. A 3,000-word essay with two AI-generated paragraphs might get a 68% AI probability score – leaving the educator with no idea which passages the model is reacting to. Sentence-level scores show exactly which sentences triggered the detection, which supports an evidence-based conversation with the student rather than a binary “you cheated” verdict.
Why are AI detectors biased against non-native English writers, and how does this approach fix it?
Non-native English writers tend to use more predictable vocabulary, shorter sentences, and simpler syntactic constructions. Perplexity-based detectors read low perplexity as a machine signal – which is also the linguistic profile of L2 writers. The fix is iterative hard negative mining: we deliberately enrich the training set with TOEFL/IELTS essay corpora, ESL thesis collections, and other formulaic academic prose, forcing the model to distinguish between “predictable because formulaic” and “predictable because machine-generated.” This drops the non-native FPR from 9.7% to 1.4% after five mining iterations.
Can the system detect text from GPT-5, Claude 4.5, and other frontier models?
Yes. Per-model accuracy ranged from 99.4% to 99.9% across GPT-5, Claude Sonnet 4.5, Gemini 2.5 Pro, Llama 4 Maverick, DeepSeek-R1, and Mistral Large 2 on our internal evaluation. The system also generalized to models it was never trained on – Qwen 3.5 (98.1%) and Grok 3 (97.6%) – which suggests it is learning general distributional properties of machine text rather than memorizing model-specific artifacts. As new models emerge, ongoing retraining is required.