The GenomeComputer Company
Back to tutorials

Tutorial

Get citations from AI answers

Teach AI tools to attach provenance to genome claims so you can see which claims came from your .genome and which came from research context.

5 minAny AI tool

What you will learn:

You will have a citation and provenance prompt you can run after any .genome answer.

A useful genome answer should be traceable. You should be able to see whether a claim came from your .genome, an annotation inside the bundle, a named source, or the model's own reasoning. Citations are not decoration. They are how you keep the answer inspectable.

Because .genome bundles are designed around AI exploration, they can carry source fields and evidence context in ways that are easier for a model to use. But the model still needs to be asked to show provenance. Without that instruction, it may summarize without telling you where the summary came from.

What provenance should include

  • The file or section of the .genome bundle used for a claim.
  • The gene, variant, pathway, or annotation being discussed.
  • The source name, paper, database, or evidence label if present.
  • Whether the claim is direct file evidence, annotation context, research context, or inference.
  • Any missing evidence that would make the answer stronger.

Citation workflow

  1. Ask your original question.
  2. Let the model produce a first answer.
  3. Ask it to add provenance to every important claim.
  4. Ask it to remove claims with no file, source, annotation, or clearly labeled inference.
  5. Ask it to return a clean version with citations inline or in a table.
  6. Save the cited version, not the first draft.

Add provenance

Add provenance to your previous answer. For each important claim, label whether it came from my .genome bundle, an annotation inside the bundle, a named external source, or your inference. Include the relevant gene, variant, file, source name, and confidence context where available.

Citation table

Convert the answer into a table with columns: claim, gene or variant, source of evidence, file or annotation used, confidence context, and follow-up question. Keep the wording concise and make unsupported claims obvious.

How to read the cited answer

  • Claims tied to a file and a source are stronger than claims tied only to general knowledge.
  • Claims tied to research context may be useful but should not be treated as direct findings from your genome.
  • Missing source fields are not automatically wrong, but they should make you ask for a stronger explanation.
  • A citation table is often easier to audit than a long paragraph.

When you ask for citations, you are not trying to make the answer academic. You are making it usable. The goal is to know where each idea came from before you decide what to explore next.