disbunkFact-checking and disinformation response
How verification works in Disbunk
Follow the Disbunk verification process: record a claim, trace its sources, preserve evidence, review findings and prepare a documented response.
Last updated:
1. Record the claim and its context
Record the exact statement, source link and relevant context. A reported claim is a starting point for investigation, not a conclusion about its truth.
2. Trace sources and preserve evidence
Find the original source, check dates and context, and collect supporting or contradicting material. Evidence files are kept with the investigation; file hashes help detect changes to a file, but do not establish that its contents are true.
3. Review findings before responding
Researchers document their reasoning and request editorial review. Verified means the reviewed evidence supports the claim; debunked means the evidence contradicts it; escalated means the case needs additional review or action. These workflow outcomes should be read with their sources and explanation.
4. Correct the record
If you identify a mistake, contact info@disbunk.org with the claim link, the disputed statement and supporting sources. The team can review the case and update its findings. This page does not promise a response deadline.
What AI clustering can and cannot do
Multilingual embeddings and HDBSCAN suggest similar recorded claims within each team. Researchers review suggestions before creating campaigns. Similarity does not prove coordination or falsity. Outliers are not deleted, and the worker does not automatically monitor the whole internet.
Access and publication
Investigation records belong to the signed-in workspace. A public explanation of a feature is not permission to access private evidence. Public fact-check result pages are not currently published automatically.