Why can an AI chatbot answer a question when a search engine cannot, and where does its answer come from?

Search retrieves documents; a chatbot writes an answer

The distinction is easiest to see as two different workflows.

flowchart LR
    Q[Your question] --> S[Search engine]
    S --> I[Search index]
    I --> R[Ranked links, snippets, maps]
    Q --> M[Chatbot]
    C[Conversation, uploaded files, instructions] --> M
    W[Optional web or document retrieval] --> M
    P[Learned model parameters] --> M
    M --> A[Newly generated answer]
    R --> V[You open and evaluate pages]
    A --> V

Visual brief: If this article is illustrated, use the diagram above as a simple two-lane flow. Give the search lane a folder or index icon and end it in several page cards. Give the chatbot lane a speech-bubble icon, show “model parameters”, “your prompt”, and optional “retrieved pages” feeding it, and end it in one drafted answer. Put a small checkmark beside the reader's final verification step in both lanes. Do not imply that the parameter box is a library of original documents.

A search engine has already discovered, crawled, and indexed some accessible pages. When you search, it looks in that index and ranks candidate pages. Google describes the basic stages as crawling, indexing, and serving results, and notes that ranking considers many signals, including relevance and context such as language, location, and device. How Google Search works, Google's ranking-systems guide. The result page is principally a navigational tool: it helps you choose a source to read.

A chatbot is principally a language-generating tool. It receives your prompt and conversation context, estimates probabilities for the next token, chooses one, then repeats. Modern LLMs use a Transformer architecture, which uses attention to weigh relationships in the provided context. The original Transformer paper, Google's accessible explanation of LLMs. It does not need to locate a page that answers your exact question before it can write a coherent answer.

This is why a chatbot is often better at questions shaped like these:

• “Explain this insurance letter in plain English and list the questions I should ask.”
• “I have these ingredients and 30 minutes. Suggest two dinners, avoiding nuts.”
• “Compare these three phone plans using the details I pasted, then show the monthly cost for my usage.”

Those are mainly tasks of explanation, transformation, comparison, or planning. A search engine can supply raw material, but it will not normally turn it into a tailored response on its own.

Conversely, search is often better when you need to find the original item: a specific manual, a local service, an exact quote, a government form, a news report, or the official rules for an event. A chatbot can help formulate that search, but it should not replace opening the result.

Two everyday examples

In the first example, there may be no existing page that exactly matches the cupboard, time limit, and dietary preference. The chatbot can create a practical synthesis. In the second, a fluent synthesis is useful only after it is grounded in the applicable official material. A generic answer could confuse an EU rail rule, a national rule, and an operator's goodwill policy.

“Sources” can mean five different things

People use “Where did the AI get that?” to mean several different things. Separating them prevents a common misunderstanding.

1. Training data: material used to teach the model patterns

Before release, a language model is trained on very large collections of text and often other data. During training, it adjusts millions or billions of numbers, called parameters, to make better predictions. Further training can teach it to follow instructions or behave better on particular tasks. Google's explanation of training and fine-tuning, Google's fine-tuning guide.

Training data is not a footnoted bibliography for each response. The model does not normally look up an original training document while answering, nor can it reliably say “this sentence came from page X.” Knowledge from training is distributed across parameter values rather than kept as a neat card catalogue. The research paper that introduced retrieval-augmented generation explicitly distinguishes a model's parameter-based memory from an external document index, and identifies provenance as a difficulty for parameter-only knowledge. Lewis et al., Retrieval-Augmented Generation.

So, “my training data includes the source” and “this answer is supported by that source today” are very different claims. Treat a base-model answer as a useful draft or explanation, not as evidence that you can cite.

2. Parameters: the model's learned, compressed patterns

Parameters are the adjustable numbers that training changes. A helpful but imperfect analogy is that training turns many examples into learned habits, not into a searchable shelf of books. The parameters can help the model explain photosynthesis, write a summary, or recognise a familiar pattern. They do not provide a dependable list of the documents that support an individual sentence.

This also explains a surprising behaviour: the model may state a correct fact in different words, combine facts it saw in different contexts, or make up a plausible-sounding detail when the pattern is weak. It is generating a continuation, not quoting a verified database record.

3. Your current context: what you supply in the conversation

The prompt, earlier messages, pasted text, uploaded files, and sometimes connected workplace data can be direct inputs to an answer. This is the most traceable kind of source if you can inspect the material yourself.

For example, if you paste three electricity bills and ask for a comparison, the chatbot may calculate from those bills. It may still make a transcription or arithmetic error, so check the numbers, but its evidential basis is clearer than a vague answer from training.

Do not paste private data merely because a chatbot is convenient. Confirm the product's data and workspace settings before sharing personal, medical, financial, client, or confidential information.

4. Retrieved documents: web search, a knowledge base, or a file search

Some chatbots can search the live web, search an index, or retrieve passages from files before drafting. This pattern is often called retrieval-augmented generation, or RAG. The retrieval system finds possibly relevant passages; the language model uses those passages and its general language ability to write the response. The classic RAG work combines a parameter-based model with an external document index. Lewis et al..

This can make an answer more current and auditable, but it is not a truth guarantee. The system may retrieve poor sources, miss the best source, misunderstand a passage, mix supported and unsupported claims, or use a source that has changed. An answer can have ten citations and still fail if none supports its key conclusion.

As one concrete product example, OpenAI says that ChatGPT's web-search answers may include citations and that readers should open them, check publication or update dates, and prefer authoritative sources when accuracy matters. OpenAI: Searching the web with ChatGPT. Other products have different retrieval systems and source displays, so check the specific product's documentation instead of assuming their behaviour is identical.

5. Citations: links intended to let you check claims

A citation is a claimed connection between an answer and a source. It is the most useful form of “source” for a reader, provided it is real and correctly placed. It does not prove that every surrounding sentence is supported. It may point to a page that is irrelevant, outdated, paywalled, misquoted, or lower quality than a primary source.

A citation is an invitation to verify, not a substitute for verification. NIST warns that generative systems can produce confidently false content, including false citations or reasoning that appears to justify an incorrect answer. NIST Generative AI Profile, section 2.2.

Why a smooth answer can be wrong

“Hallucination” is the popular term for an answer that is invented or false but sounds plausible. NIST uses the more neutral word confabulation for confidently stated erroneous or false content. NIST Generative AI Profile. The failure is not necessarily a deliberate deception. The model is optimising for a likely, helpful continuation of the conversation, not independently proving each proposition.

Common causes include:

• The question assumes a false premise, but the model accepts it instead of challenging it.
• The fact has changed since training, such as a price, office-holder, policy, product feature, or timetable.
• The prompt lacks location, date, product version, or other decisive context.
• The answer requires an exact quotation, calculation, legal rule, or citation that the model has not retrieved.
• Retrieved sources disagree, are low quality, or are being summarised too broadly.

Fluency is therefore a poor reliability signal. The better signals are a specific claim, a relevant primary source, a visible date and jurisdiction where relevant, agreement with another independent authoritative source, and a calculation you can reproduce.

Base-model answers and web-enabled answers are different modes

Before relying on a response, establish which mode you are in.

The modes can overlap. A web-enabled chatbot does not stop using its learned parameters when it searches, and a base model may have learned some old version of a fact. The practical rule is simple: if a claim needs to be current, attributable, or defensible, ask for sources and verify the important ones directly.

A practical workflow for checking an AI answer

Use this workflow when an answer will influence a purchase, travel, health decision, legal question, school work, work output, or public claim.

1. Classify the claim. Is it a creative suggestion, a stable explanation, a current fact, a calculation, or a high-stakes instruction? The more current or consequential it is, the more checking it deserves.
2. Ask for the evidence you actually need. Try: “Use current primary sources. Give a link directly after each factual claim. State the country, date, and any assumptions.” For a calculation, ask it to show inputs and arithmetic.
3. Open the two or three most important citations. Start with an official regulator, manufacturer, public body, original study, or contract, not a blog that repeats one.
4. Test entailment, not just topic match. Find the sentence, table, or rule in the source. Does it really say what the chatbot says? A source about delays in general does not prove a refund for your ticket.
5. Check scope and freshness. Note the publication or update date, country, product version, eligibility criteria, and exceptions. Search ranking and a citation list do not replace this contextual check.
6. Cross-check a consequential conclusion. Use a second independent authoritative source, or contact the responsible organisation. For medical, legal, tax, safety, or investment decisions, professional advice or the official authority may be necessary.
7. Keep the source, not only the summary. Bookmark or save the official page and record its date if you need to defend the decision later.

If the chatbot gives no sources

Do not ask only “Are you sure?” That often produces more fluent wording rather than better evidence. Instead:

1. Ask whether the answer was based on web search, supplied files, connected data, or general model knowledge.
2. Ask it to separate claims that need current evidence from its reasoning or recommendations.
3. Request direct, primary-source URLs, dates, and quotations no longer than necessary to locate the relevant passage.
4. If it cannot provide checkable evidence, treat its output as an unverified explanation. Search for the primary source yourself or use a search-enabled research tool.

For a low-stakes task such as a meal plan, that may be enough. For a decision with legal, medical, financial, privacy, or safety consequences, lack of sources is a reason to pause, not a reason to trust confidence.

If a citation does not support the claim

Open the link. Check whether it is the correct page, whether it is current, and whether it supports the exact claim rather than a nearby but different one. Then tell the chatbot precisely what failed:

“This link describes general passenger rights, but it does not state that my ticket is refundable. Revise the answer using the operator's current conditions of carriage and quote the relevant clause.”

Do not accept a replacement citation without opening that one too. A source that does not support a claim should be removed or the claim narrowed. If the sources conflict, say so in the final wording rather than forcing a single confident conclusion.

A sensible division of labour

Use a search engine to locate original sources, compare perspectives, and inspect the material. Use a chatbot to turn well-specified material into a clearer explanation, a checklist, a draft, a comparison, or follow-up questions. Use your own judgment, and where the stakes warrant it, an accountable expert or official authority, to make the final decision.

The two tools are complements. The most reliable pattern is often: search or retrieve good evidence, read the key sources, then let the chatbot help you understand and organise them while keeping the links visible.