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

推荐订阅源

T
Threat Research - Cisco Blogs
博客园 - 聂微东
小众软件
小众软件
P
Proofpoint News Feed
Security Archives - TechRepublic
Security Archives - TechRepublic
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
TaoSecurity Blog
TaoSecurity Blog
博客园 - 司徒正美
罗磊的独立博客
N
News and Events Feed by Topic
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
S
Security Affairs
S
Security @ Cisco Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
月光博客
月光博客
S
Secure Thoughts
P
Proofpoint News Feed
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Forbes - Security
Forbes - Security
H
Heimdal Security Blog
W
WeLiveSecurity
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
L
LangChain Blog
T
The Blog of Author Tim Ferriss
NISL@THU
NISL@THU
Google DeepMind News
Google DeepMind News
Cloudbric
Cloudbric
H
Hacker News: Front Page
The Last Watchdog
The Last Watchdog
Hacker News - Newest:
Hacker News - Newest: "LLM"
C
Cisco Blogs
博客园 - 三生石上(FineUI控件)
博客园_首页
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
S
Schneier on Security
Project Zero
Project Zero
SecWiki News
SecWiki News
爱范儿
爱范儿
The Register - Security
The Register - Security
AI
AI
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Y
Y Combinator Blog
L
Lohrmann on Cybersecurity
Application and Cybersecurity Blog
Application and Cybersecurity Blog
P
Privacy International News Feed
J
Java Code Geeks
S
Securelist
C
Cyber Attacks, Cyber Crime and Cyber Security
V
Visual Studio Blog

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 Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Build a Fact-Checking Pipeline for AI-Generated Content: Real-Time Verification Using Claude API
binky · 2026-06-01 · via DEV Community

Your content creators are publishing unverified claims generated by AI, and manual fact-checking is a bottleneck. Here's the exact Python pipeline I built to automatically extract claims, verify them across 3 data sources, and flag risky content—copy-paste ready with working code.

I built this after watching a client's editorial team spend 4 hours manually checking a single 2,000-word AI-generated article. At that rate, fact-checking consumed 60% of their publishing workflow. The fix wasn't hiring more editors—it was automating the first pass entirely.

The Problem: Why Manual Fact-Checking Kills Creator Productivity

The average AI-generated article contains 3-7 factual claims that need external verification. At 15 minutes per claim, a 10-article daily pipeline burns 7-17 hours of editor time per day. That's before anyone touches tone, structure, or SEO.

The deeper issue: LLMs hallucinate with confidence. Claude, GPT-4, Gemini—they all produce fluent, authoritative-sounding text for claims that are flat wrong. Standard content QA doesn't catch this because editors scan for coherence, not factual accuracy.

What we need is a system that extracts every verifiable claim, scores it against real data, and surfaces only the risky ones for human review. Editors stop reading everything and start reviewing exceptions.

Architecture Overview: Building a Modular Verification Pipeline

The pipeline has four stages running in sequence:

  1. Claim Extraction — Claude with extended thinking parses the article and pulls discrete, verifiable claims
  2. Multi-Source Verification — Each claim hits Wikipedia API and SerpAPI in parallel
  3. Confidence Scoring — Results get weighted into a 0–1 confidence score per claim
  4. Output & Integration — JSON output consumed by CLI, webhook, or your CMS

Each stage is a separate Python class. You can swap out the verification sources without touching the scoring engine. I'll show you the full wiring at the end.

Part 1: Setting Up Claude API with Extended Thinking for Claim Extraction

Install dependencies first:

pip install anthropic requests python-dotenv serpapi

Enter fullscreen mode Exit fullscreen mode

Extended thinking is the key here. Standard Claude responses give you a flat list of claims. With extended thinking enabled, Claude actually reasons about which statements in the text are verifiable facts versus opinions versus hypotheticals—the extraction quality is measurably better.

import anthropic
import json
import os
from dotenv import load_dotenv

load_dotenv()

class ClaimExtractor:
    def __init__(self):
        self.client = anthropic.Anthropic(api_key=os.getenv("ANTHROPIC_API_KEY"))
        self.model = "claude-claude-3-7-sonnet-20250219"

    def extract_claims(self, article_text: str) -> list[dict]:
        """
        Extract verifiable factual claims from article text using extended thinking.
        Returns a list of claim dicts with 'claim', 'context', and 'verifiability' keys.
        """
        prompt = f"""Analyze the following article and extract all verifiable factual claims.

For each claim, provide:
- claim: The specific factual statement (concise, self-contained)
- context: The surrounding sentence for reference
- verifiability: "high" (specific facts/numbers/dates), "medium" (general assertions), or "low" (opinions/predictions)

Only include claims that can be checked against external sources. Skip pure opinions.

Return a JSON array of claim objects. No other text.

Article:
{article_text}"""

        response = self.client.messages.create(
            model=self.model,
            max_tokens=16000,
            thinking={
                "type": "enabled",
                "budget_tokens": 10000
            },
            messages=[{"role": "user", "content": prompt}]
        )

        # Extract text content from response (thinking blocks are separate)
        text_content = ""
        for block in response.content:
            if block.type == "text":
                text_content = block.text
                break

        try:
            claims = json.loads(text_content)
            return claims
        except json.JSONDecodeError:
            # Strip markdown code fences if Claude wrapped the JSON
            cleaned = text_content.strip().removeprefix("```

json").removesuffix("

```").strip()
            return json.loads(cleaned)

Enter fullscreen mode Exit fullscreen mode

The extract_claims method sends the article to Claude with thinking.budget_tokens set to 10,000—enough reasoning budget to distinguish genuine factual claims from hedged statements. The response content is a mix of thinking blocks and text blocks, so we explicitly filter for block.type == "text" to get the JSON.

Part 2: Multi-Source Verification

Each claim gets checked against Wikipedia (good for established facts) and SerpAPI (good for recent events and statistics). Running them in parallel with concurrent.futures keeps latency under 3 seconds per batch.

import requests
import time
from concurrent.futures import ThreadPoolExecutor, as_completed
from serpapi import GoogleSearch

class MultiSourceVerifier:
    def __init__(self):
        self.serp_api_key = os.getenv("SERPAPI_KEY")
        self.wiki_base = "https://en.wikipedia.org/api/rest_v1/page/summary/"
        self.wiki_search = "https://en.wikipedia.org/w/api.php"

    def verify_claim(self, claim: dict) -> dict:
        """Run Wikipedia and SerpAPI checks in parallel for a single claim."""
        with ThreadPoolExecutor(max_workers=2) as executor:
            futures = {
                executor.submit(self._check_wikipedia, claim["claim"]): "wikipedia",
                executor.submit(self._check_serp, claim["claim"]): "serp"
            }
            results = {}
            for future in as_completed(futures):
                source = futures[future]
                try:
                    results[source] = future.result(timeout=5)
                except Exception as e:
                    results[source] = {"status": "error", "error": str(e)}

        return {
            "claim": claim["claim"],
            "context": claim.get("context", ""),
            "verifiability": claim.get("verifiability", "medium"),
            "sources": results
        }

    def _check_wikipedia(self, claim_text: str) -> dict:
        """Search Wikipedia for relevant content and return snippet + confidence signal."""
        search_params = {
            "action": "query",
            "list": "search",
            "srsearch": claim_text,
            "format": "json",
            "srlimit": 3
        }
        resp = requests.get(self.wiki_search, params=search_params, timeout=5)
        resp.raise_for_status()
        data = resp.json()

        search_results = data.get("query", {}).get("search", [])
        if not search_results:
            return {"status": "not_found", "snippets": []}

        # Grab the top result's summary via REST API
        top_title = search_results[0]["title"].replace(" ", "_")
        summary_resp = requests.get(f"{self.wiki_base}{top_title}", timeout=5)

        snippets = [r.get("snippet", "") for r in search_results[:3]]
        summary = ""
        if summary_resp.status_code == 200:
            summary = summary_resp.json().get("extract", "")[:500]

        return {
            "status": "found",
            "top_title": search_results[0]["title"],
            "summary": summary,
            "snippets": snippets
        }

    def _check_serp(self, claim_text: str) -> dict:
        """Run a Google search via SerpAPI and return top organic results."""
        params = {
            "q": claim_text,
            "api_key": self.serp_api_key,
            "num": 5,
            "gl": "us",
            "hl": "en"
        }
        search = GoogleSearch(params)
        results = search.get_dict()

        organic = results.get("organic_results", [])[:3]
        snippets = [
            {"title": r.get("title", ""), "snippet": r.get("snippet", ""), "link": r.get("link", "")}
            for r in organic
        ]

        return {
            "status": "found" if snippets else "not_found",
            "results": snippets
        }

    def verify_all(self, claims: list[dict]) -> list[dict]:
        """Verify a full list of claims, with rate-limit-friendly delays."""
        verified = []
        for i, claim in enumerate(claims):
            verified.append(self.verify_claim(claim))
            if i < len(claims) - 1:
                time.sleep(0.5)  # Respect SerpAPI rate limits
        return verified

Enter fullscreen mode Exit fullscreen mode

verify_all processes claims sequentially with a 0.5s delay between SerpAPI calls—I learned this the hard way after hitting 429s on a 15-claim batch. The verify_claim method runs Wikipedia and SerpAPI in parallel per claim, so total latency per claim is ~2-3 seconds instead of 5-6.

The bug I hit: I originally used claim["claim"] directly as the Wikipedia REST API title lookup, which failed 80% of the time. Wikipedia's REST title endpoint is exact-match. The fix was using the opensearch action to find the right article title first, then fetching the summary—that's the two-step approach you see in _check_wikipedia.

Part 3: Building the Confidence Score Engine

Raw search results don't mean much without a scoring layer. I weight Wikipedia higher for historical facts, SerpAPI higher for recent statistics, and discount both when the claim has high verifiability stakes.

import re
from dataclasses import dataclass

@dataclass
class ScoredClaim:
    claim: str
    context: str
    confidence: float  # 0.0 = unverified/risky, 1.0 = well-supported
    risk_level: str    # "low", "medium", "high", "critical"
    flag_for_review: bool
    reasoning: str
    raw_sources: dict

class ConfidenceScorer:

    VERIFIABILITY_WEIGHTS = {
        "high": {"wikipedia": 0.45, "serp": 0.55},
        "medium": {"wikipedia": 0.55, "serp": 0.45},
        "low": {"wikipedia": 0.60, "serp": 0.40}
    }

    def score_claim(self, verified_claim: dict) -> ScoredClaim:
        verifiability = verified_claim.get("verifiability", "medium")
        weights = self.VERIFIABILITY_WEIGHTS[verifiability]
        sources = verified_claim.get("sources", {})

        wiki_score = self._score_wikipedia(sources.get("wikipedia", {}))
        serp_score = self._score_serp(sources.get("serp", {}), verified_claim["claim"])

        weighted_score = (wiki_score * weights["wikipedia"]) + (serp_score * weights["serp"])

        # Penalty: high-verifiability claims with no Wikipedia hit are riskier
        if verifiability == "high" and sources.get("wikipedia", {}).get("status") == "not_found":
            weighted_score *= 0.7

        risk_level = self._risk_level(weighted_score)
        flag = risk_level in ("high", "critical")

        reasoning = (
            f"Wikipedia score: {wiki_score:.2f} (weight {weights['wikipedia']}), "
            f"SERP score: {serp_score:.2f} (weight {weights['serp']}). "
            f"Final: {weighted_score:.2f}. Verifiability: {verifiability}."
        )

        return ScoredClaim(
            claim=verified_claim["claim"],
            context=verified_claim.get("context", ""),
            confidence=round(weighted_score, 3),
            risk_level=risk_level,
            flag_for_review=flag,
            reasoning=reasoning,
            raw_sources=sources
        )

    def _score_wikipedia(self, wiki_result: dict) -> float:
        if wiki_result.get("status") == "error":
            return 0.3
        if wiki_result.get("status") == "not_found":
            return 0.2
        # Has summary = good signal. Has snippets = bonus.
        score = 0.6
        if wiki_result.get("summary"):
            score += 0.25
        if len(wiki_result.get("snippets", [])) >= 2:
            score += 0.15
        return min(score, 1.0)

    def _score_serp(self, serp_result: dict, claim_text: str) -> float:
        if serp_result.get("status") == "error":
            return 0.3
        results = serp_result.get("results", [])
        if not results:
            return 0.2

        claim_words = set(re.findall(r'\b\w{4,}\b', claim_text.lower()))
        score = 0.4
        for result in results[:3]:
            snippet = (result.get("snippet", "") + result.get("title", "")).lower()
            overlap = len(claim_words & set(re.findall(r'\b\w{4,}\b', snippet)))
            if overlap >= 3:
                score += 0.2
            elif overlap >= 1:
                score += 0.1
        return min(score, 1.0)

    def _risk_level(self, score: float) -> str:
        if score >= 0.75:
            return "low"
        elif score >= 0.55:
            return "medium"
        elif score >= 0.35:
            return "high"
        else:
            return "critical"

    def score_all(self, verified_claims: list[dict]) -> list[ScoredClaim]:
        return [self.score_claim(c) for c in verified_claims]

Enter fullscreen mode Exit fullscreen mode

The _score_serp method uses keyword overlap between the claim and search snippets rather than semantic similarity—it's rougher but doesn't require an embeddings API call, keeping the pipeline fast. Any claim scoring below 0.55 gets flagged for human review.

Part 4: Integration — CLI Tool + JSON Output

Wire everything together into a single runnable script with CLI arguments:


python
#!/usr/bin/env python3
"""
factcheck.py — AI Content Fact-Checking Pipeline
Usage: python factcheck.py --input article.txt --output results.json
"""

import argparse
import json
import sys
from dataclasses import asdict

def run_pipeline(article_text: str) -> dict:
    extractor = ClaimExtractor()
    verifier = MultiSourceVerifier()
    scorer = ConfidenceScorer()

    print("📋 Extracting claims...", file=sys.stderr)
    claims = extractor.extract_claims(article_text)
    print(f"   Found {len(claims)} verifiable claims", file=sys.stderr)

    print("🔍 Verifying against external sources...", file=sys.stderr)
    verified = verifier.verify_all(claims)

    print("📊 Scoring confidence...", file=sys.stderr)
    scored = scorer.score_all(verified)

    flagged = [c for c in scored if c.flag_for_review]
    avg_confidence = sum(c.confidence for c in scored) / len(scored) if scored else 0

    output = {
        "summary": {
            "total_claims": len(scored),
            "flagged_for_review": len(flagged),
            "average_confidence": round(avg_confidence, 3),
            "recommendation": "HOLD" if len(flagged) > 2 else "APPROVE_WITH_REVIEW" if flagged else "APPROVE"
        },
        "flagged_claims": [asdict(c) for c in flagged],
        "all_claims": [asdict(c) for c in scored]
    }
    return output

def

---

*Follow for more practical AI and productivity content.*

Enter fullscreen mode Exit fullscreen mode