AiNerd.sg Contact
Journal index

Field guide

Start with your sources

A small, repeatable exercise for getting useful answers from source-grounded AI without confusing a citation with proof.

The most useful first AI experiment may already be in your reading folder. Choose a question you care about and a few documents you can inspect yourself. A small collection makes it easier to see what the system used, what it missed, and where your own question needs sharpening.

Google’s source-based notebook tool, known as NotebookLM and currently described as Gemini Notebook in its help documentation, supports asking questions about uploaded material and selecting which sources a response should use. Its citations let you open the relevant material in context. That makes it a useful setting for learning an evidence-checking habit.

Build a deliberately small notebook

For an exercise, choose two or three public documents on the same topic: perhaps a framework’s introduction, its installation guide, and a migration guide. Record their titles and dates. Avoid beginning with a whole library; you want to recognise the material well enough to catch omissions.

Set one narrow question. “What should I read?” is difficult to assess. “Which steps does this installation guide require before running the first example?” has a result you can compare against the guide.

Ask for evidence and gaps

Try a prompt like this:

Using only the selected sources, list the prerequisites for running the example. Give a citation for each requirement. Separate explicit requirements from your interpretation. If a requirement is unclear, say what information is missing.

This is a proposed exercise, not a guarantee about the response. Inspect what comes back. Did the answer combine instructions for two versions? Did it turn a recommendation into a requirement? Did a citation support the whole sentence or only its first clause?

Follow the citation back

Read the surrounding paragraph, not just the highlighted phrase. Check the heading above it: a correct instruction for one operating system can be misleading when applied to another. If the answer says a feature is supported, look for the conditions attached to that support.

Keep a compact note with three columns: claim, supporting passage, and remaining question. Writing down the gap is often more useful than asking the system to produce another polished summary.

Add complexity slowly

Once the narrow question works, add a document that presents a different perspective. Ask where the sources agree and where they differ. Distinguish a factual disagreement from different dates, audiences, or assumptions.

For a learning session, finish by explaining the topic in your own words and checking that explanation against the documents. The notebook helps you navigate and compare material. Your understanding grows when you can trace the important claims yourself.