A table is not its own interpretation. These 15 prompts walk you through reading data carefully — distinguishing description from inference, surfacing effect sizes, hunting confounders, spotting visual misuse, and writing exam-ready or thesis-ready narrative.
Who this is for
Statistics and methods students, researchers reading new datasets, journalists processing data releases, business analysts producing decks, and anyone preparing data sections for a paper.
When not to use these prompts
Skip these for trivial data (“our 5-person poll”). Skip too if you need rigorous statistical analysis; AI suggests interpretations but does not replace a statistician on consequential decisions.
Prompt anatomy / structure formula
A data-interpretation prompt should always carry six elements:
- Role: who the AI plays — research tutor, peer reviewer, exam coach, debate partner, librarian.
- Context: your level, subject, deadline, paper count, target citation style, course or program.
- Goal: one concrete deliverable — 12 quiz items, a 1-page lit matrix, 5 counter-arguments, a 4-week revision plan.
- Constraints: word count, depth, source types allowed, what to skip, what to never claim.
- Output format: numbered list, table, JSON, or graded blocks (E / M / H) so you can paste into Notion / Anki / Word.
- Examples / signal: 1-2 reference paragraphs or anti-examples (“not the way Wikipedia explains it”).
Best for
- Stats homework / lab report writing
- Thesis results section drafting
- Data journalism explainers
- Exam answer for chart-reading questions
- Business deck narrative for analytics
15 copy-ready prompt templates
1. Descriptive-first read
Default first read; resist inference until description is solid.
You are a data tutor. Below is a data table / chart description. (1) Describe what it shows in 3 plain sentences (no inference yet). (2) List the 3 most striking patterns. (3) Identify what we cannot conclude from this data alone. No causal language until the next step.
{paste data}Variables to swap: data description
Optimization: If AI jumps to inference, add: “Strictly descriptive in this step. Any sentence that uses cause / effect / leads / drives should be removed.”
2. Effect-size honesty
Below is a result: {paste statistic, e.g., r=0.18, p less than .05, n=420}. Translate this into plain language: what does the effect size mean in practice, how confident should I be, what the p-value does and does not tell me. End with: "this finding should change your behavior by..." or "...should not change your behavior because...".3. Confounder hunt
I observed that {variable A} correlates with {variable B} in dataset {context}. List 5 plausible confounders, why each could explain the correlation, and what additional data would help distinguish them.4. Chart-misuse audit
Below is a description of a chart. Audit it for common visual misuse: truncated y-axis, dual axes without justification, area-vs-length confusion (3D pies), cherry-picked baseline, misleading color scales. Suggest a fixed version.
{paste chart description}5. Confidence interval explainer
Explain this confidence interval in plain language for a {audience — undergraduate / executive / journalist}: {paste CI}. Cover: what it means, what it does not mean (common misinterpretation), one practical implication.6. “What is missing” probe
Below is a data summary. List 5 things that are missing or unclear: denominator, time window, sample frame, missing-data handling, outlier treatment. For each: how it could change the interpretation if addressed.
{paste summary}7. Compare-two-results
Compare these two results: {result A} and {result B}. Note: (a) which has the larger effect, (b) which is more precise, (c) which is more generalizable, (d) which deserves more weight in a decision and why.8. Reasonable-skeptic stress-test
Pretend you are a skeptical reviewer. Below is my interpretation of the data. List 5 alternative interpretations consistent with the same data and 1 piece of additional evidence that would discriminate between them.
{paste my interpretation}9. Bayesian common-sense check
A study found {result}. Apply a common-sense Bayesian update: what was a reasonable prior before the study, how strong is this evidence, what should my posterior be? Express each step in plain language, no formulas required.10. Multiple-testing alarm
The paper tested {N} hypotheses and reported {M} significant at p less than .05. Estimate how many we would expect to be "significant" by chance alone. Discuss whether the authors corrected for multiple comparisons and what to look for in the methods.11. Lay-audience narrative
Translate this data result into a 150-word plain-language story for a non-technical reader: setup, what was found, what it means, one caveat. Do not omit numbers; humanize them with comparisons (per 1000 people, per year, etc.).
{paste}12. Decision-relevant takeaway
For a {decision-maker role} reading this data, what 3 takeaways actually matter for action? For each: the data point, the recommended action, the threshold at which the action should be revisited.
{paste data}13. Results-section paragraph
Draft a 200-word results section paragraph for a {social science / clinical / engineering} paper based on the following findings: {paste numbers}. Use neutral, descriptive academic voice; cite the statistical test, effect size, and CI / p-value.14. Visualization improvement
Describe a better way to visualize this data, given my audience is {audience}: type of chart, key annotations, what to highlight, what to drop. Justify each choice in 1 sentence.
{paste data}15. Limitations paragraph for data section
Write a 150-word limitations paragraph for this data analysis: sampling, measurement, missing data, generalizability. End with the single most important caveat a reader should remember.
{paste study summary}Common mistakes
- Jumping straight to “X causes Y” from a correlation.
- Reporting p-values without effect sizes — small effects can be “significant” but useless.
- Forgetting denominators — 30% of what? n=10 or n=10000?
- Trusting AI math without spot-checking — always verify reported numbers against the source.
- Ignoring missing data — what was dropped often matters more than what was reported.
- Treating one study as a final answer; meta-analysis trumps single results.
- Reading the title and abstract instead of methods and figures.
How to push results further
- Always do descriptive read first (template 1) before any inferential language.
- For every result, ask “compared to what?” and “in what units?”
- Cross-check AI calculations on a calculator or in spreadsheet for any decision-relevant number.
- Visualize the data yourself; reading a table and reading a chart give different insights.
- Use template 8 (skeptic stress-test) once per claim you intend to publish or present.
- For lay communication, humanize numbers (template 11): “per 1000 people, per year” beats raw percentages.
- Save a personal “common chart misuses” file; pattern recognition saves time on future audits.
FAQ
- Can AI run statistical analysis?: It can suggest what tests fit, interpret outputs, and write up results. For computation, use proper tools (R / Python / SPSS / Stata).
- How do I know an AI interpretation is right?: Cross-check effect sizes, denominators, and units against the source data. Run template 8 (skeptic stress-test) before relying on it.
- What is the most common mistake in data interpretation?: Conflating statistical significance with practical importance. Always report effect size in plain units.
- Should I use AI for my thesis stats section?: Use it to draft and check narrative; do not let it run the analysis or judge fit of statistical tests for consequential decisions.
- How do I handle confounders without controlled experiments?: List the plausible ones (template 3), test where you can with stratification or matching, and acknowledge the rest in limitations.