Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


To get AI to cite sources use a bounded question, require a source for each important claim, and then check the reference yourself. A link or footnote is a useful trail, not a guarantee: OpenAI warns that ChatGPT can produce fabricated citations or misrepresent what a source says.[1]
For the wider habit of asking for evidence and marking uncertainty, see the wider evidence-checking routine for AI output. This guide focuses on a narrower job: turning an AI answer into a claim/evidence worksheet that another person can audit.
Key Takeaways
- Split a response into claims before you look at its references.
- Ask for stable source details, not just a list of links.
- Check that the source exists, is authoritative for the claim, and actually supports it.
- Preserve dates, qualifiers, population, and definitions when you paraphrase.
- Mark a claim as unsupported or uncertain instead of upgrading a plausible sentence.
An AI system predicts text. It can produce a realistic-looking title, URL, author, quote, or page number even when the item does not exist. It can also attach a real source to a sentence that the source never made. OpenAI’s guidance describes these “fake citations” as a known failure mode and recommends verifying important information in the original source.[1]
The distinction is simple:
| Item | What it tells you | What it does not tell you |
|---|---|---|
| Citation exists | The answer includes a reference-shaped object | The page is real or relevant |
| Source is real | You can open the page or document | The source supports this exact claim |
| Passage is relevant | The words concern the topic | The passage proves causation, currentness, or generality |
| Evidence is sufficient | The claim survives your defined test | The claim is safe for every decision |
Treat each row as a separate test. If a high-stakes claim fails one test, do not rescue it with better prose.
Copy the draft into a worksheet and split compound sentences. “The policy reduced fraud by 20% and works for all customers” contains at least two claims: a measured change and a generalization. They may need different sources and different checks.
Use one row per claim:
| Claim ID | Claim as written | Needed evidence | Risk if wrong |
|---|---|---|---|
| C1 | The policy reduced reported fraud | A dated measurement with a defined comparison | A decision may overstate impact |
| C2 | The result applies to all customers | Population and sampling evidence | A group may be excluded |
| C3 | The policy is still in force | Current official policy page | Readers may follow an old rule |
Keep the original wording in one column and your cautious rewrite in another. This makes it harder to forget a qualifier while editing for fluency.
Do not ask only “add sources.” Tell the model what a usable source record contains and what to do when it cannot find one. For example:
For each claim below, provide one or two public sources. Return a table with claim ID, source title, publisher, publication date, URL, supporting passage or section, and a one-sentence limitation. Use only sources you can identify. If a source cannot be verified, write “unverified” and do not invent a URL or quotation. Separate facts from your interpretation.
Give the model the claims and the allowed source boundary. If you already have a source set, name the documents or pages. If the topic is current, add a date requirement and ask it to flag older material.
The screenshot shows a synthetic prompt in a public Gemini zero-state interface. It is not a submitted answer and contains no account or client data.
The contract creates an acceptance test. A response that omits the publisher, date, limitation, or verification state is incomplete even if its links look convincing.
Open each URL yourself. For a document, use the official publisher, repository, DOI record, or primary dataset rather than a copied summary. Check:
If a URL returns a login wall, redirect, or unrelated page, mark the source unverified. Do not infer that it exists from the model’s confidence.
For a law or policy, start with the issuing authority. For a measurement, start with the dataset or methods section. For a product capability, start with the vendor’s current documentation and state that availability can depend on account, region, or plan. A secondary article can help you find a primary source, but it should not silently replace it.
Read enough context around the passage to understand its subject, conditions, and exceptions. Then classify the relationship:
| Result | Meaning | Safe wording |
|---|---|---|
| Supported | The passage states the claim under the same conditions | “The report states…” |
| Partly supported | The passage supports only a narrower version | “In the studied group…” |
| Contradicted | The passage says something different | “The source does not support this statement” |
| Not found | You cannot locate the claimed evidence | “No supporting passage found” |
| Unclear | The source or context is inaccessible | “Verification pending” |
Watch for common upgrades:
Preserve the source’s limits in your rewrite. If the original says “among respondents in one city,” keep that boundary in the sentence and in the worksheet.
If the model supplies a quotation, search the source for the exact wording and confirm that nearby sentences do not reverse its meaning. Short excerpts are easier to audit and less likely to exceed a publisher's reuse policy. If the quote is not present, replace it with a clearly labeled paraphrase or mark the claim unsupported.
For a paraphrase, compare subject, verb, number, date, condition, and conclusion. A small change in “could” to “does” can change the risk of an operational instruction. Ask the model for a diff or a list of changed qualifiers, but make the final comparison yourself.
Use a compact claim/evidence table in your working document:
| ID | Claim | Source | Passage checked | Result | Limitation | Owner |
|---|---|---|---|---|---|---|
| C1 | The policy reduced reported fraud | Official evaluation, p. 8 | “…” | Partly supported | One region, six months | Analyst |
| C2 | The result applies to all customers | Same evaluation | No population-wide test | Not found | Sample excludes new accounts | Reviewer |
The owner column prevents a worksheet from becoming a decorative appendix. Give unresolved rows to a named reviewer and keep them out of the summary until the reviewer closes them.
For health, law, finance, employment, safety, identity, or production changes, require a primary source and an accountable human reviewer. If the source is inaccessible, out of date, or only indirectly related, stop and ask for better evidence. NIST’s generative-AI profile emphasizes documenting risks, limitations, and human oversight rather than treating generated text as an unquestioned authority.[2]
Use the publisher’s search or site navigation to locate the current source. Record the mismatch and remove the model-generated URL from the draft. Never fix a broken citation by guessing a nearby slug.
Split the claims and ask which sentence the source supports. Add a second source only when it covers a distinct proposition; do not inflate a bibliography without improving coverage.
Add the population, date, method, or confidence range from the surrounding passage. If the limitation changes the conclusion, rewrite the claim rather than hiding the detail in a footnote.
Treat a snippet as a discovery hint. Open the page, identify the publisher and date, and cite the page itself. Search ranking is not evidence of authority.
Restate the output contract and require a verification column. If it still fills gaps, move the answer into the “unverified” queue and verify the claims outside the model.
Before publishing or acting on an AI-assisted answer:
For a team, store the worksheet with the draft and ask a second person to sample the highest-risk rows. The purpose is not to make every sentence sound cautious; it is to make the reasoning traceable.
Reliable AI citations come from a repeatable check, not a special prompt. Define claims, request a complete source record, open the original, compare the passage with the wording, preserve limits, and assign unresolved rows to a human owner.
Request the source title, publisher, date, stable URL, supporting passage or section, and a limitation. Add a verification state so missing evidence is explicit rather than silently omitted.
Read the cited passage and its surrounding context. Check the subject, measurement, date, population, definitions, and qualifiers against the sentence you plan to publish.
No. Authority makes a source worth examining, not automatically conclusive. Check its method, scope, date, and limitations, and compare it with another primary source when the decision matters.
Usually remove it from the conclusion or label it as an unverified lead. Keep it in a research queue only if a person is assigned to find and assess the missing evidence.
It can help find mismatches, but it is not a substitute for opening the source. Use another model as a review aid and keep the primary-source check outside the model.
There is no universal number. Use enough authoritative sources to cover the claims and their important limitations. One excellent primary source can be better than five unrelated links.
Record the citation and the access limitation, then find a lawful public abstract, repository copy, or qualified reviewer who can inspect the full text. Do not treat a summary as equivalent without saying so.
Sources:
Sources checked 23 August 2026.
Related Articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.