惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

D
Docker
Apple Machine Learning Research
Apple Machine Learning Research
宝玉的分享
宝玉的分享
博客园 - 叶小钗
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 司徒正美
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - Franky
爱范儿
爱范儿
罗磊的独立博客
IT之家
IT之家
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
N
Netflix TechBlog - Medium
云风的 BLOG
云风的 BLOG
P
Proofpoint News Feed
U
Unit 42
Engineering at Meta
Engineering at Meta
WordPress大学
WordPress大学
博客园 - 三生石上(FineUI控件)
T
Tailwind CSS Blog
H
Help Net Security
博客园_首页
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
人人都是产品经理
人人都是产品经理

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How do you know an LLM answer is actually grounded — not ...
Brian Barbour · 2026-06-04 · via DEV Community

Brian Barbour

I built a pipeline, solo, that audits LLM answers against the source text they're supposed to be grounded in — and ran it across 7 models and 4 regulated corpora. Sharing the method and the full results; I'd
like technical criticism. Veritrooper

## The problem

When an LLM answers over your documents, "sounds right" and "is right" are different things. A fluent answer can quietly fabricate a number, flip a direction, or confidently answer a question the source
doesn't actually address. In a regulated domain — tax, safety, drug labels, financial filings — that gap matters.

## What it does

For a body of written rules, the harness:

  • Generates ~1,000 questions from the source text, including deliberately unanswerable ones, to catch a model that bluffs instead of saying "not in the evidence."
  • Has the model answer with the source in context, then runs deterministic code over the answer — numbers must trace back to the source, direction/polarity must match, refusals on unanswerable questions are credited. The model is kept to prose; the checking is code.
  • Routes flagged answers to a diagnostic stage, and sends only the contested ones (~4%) to a frontier model from a different vendor — so no model gets the final word on its own output.
  • Detects malformed auto-generated questions and drops them from both arms' denominators, symmetrically.

## The experiment

Four regulated corpora: IRS tax code, OSHA 29 CFR, FDA drug labels, SEC 10-Ks. Seven models, from a 7B local model up through three frontier vendors.

The baseline isn't a straw-man — it's the same model with ordinary BM25 retrieval (top-5 chunks), a normal RAG setup. The audited column is that model handed the correct source passage and then
checked. The gap is roughly the accuracy ordinary retrieval leaves on the table.

A slice (IRS tax code):

| Model | Baseline (BM25 RAG) | Audited |
|---|---|---|
| Claude Opus 4.8 | 94.36% | 100.00% |
| GPT-5.5 | 93.04% | 99.70% |
| Qwen 2.5 72B | 86.76% | 98.19% |
| Qwen 2.5 7B | 86.58% | 96.67% |

Across all 7 models, audited accuracy lands in the ~95–100% band on most runs. The full 7×4 matrix — baseline and audited, nothing cherry-picked, including a weak 70B model that stays low — is here:

https://veritrooper.com/audit.html

Every number reconstructs from downloadable run records: every question, the model's answer, the expected answer, and the grading rationale. You can check the work, not take my word for it.

## What I'm curious about

How do others measure whether a RAG answer is genuinely grounded vs. merely plausible — a single judge-LLM, or something cross-model? Where would you poke holes in this?