Can AI find causes from data?
Only partly. Causal discovery algorithms read the patterns chains, forks and colliders leave in data, but chains and forks leave the same fingerprint, so observational data usually narrow things to a family of maps, not one. Language models can suggest plausible arrows but make many mistakes on formal causal reasoning. Use AI as a drafting partner.
Last time's quick check: a shuffled treatment has nothing to do with the outcome, so any "effect" it shows is the method finding noise. Wouldn't it be easier if a computer drew the causal map for you? Feed it the data, get back the arrows. That's causal discovery, and it's one of the most active areas of AI research.
Discovery algorithms read fingerprints. Recall Module 2: chains, forks and colliders leave different patterns of what moves with what. A collider is distinctive, because its two causes are unrelated until you hold it fixed. In 1991, Peter Spirtes and Clark Glymour published an algorithm, known as PC after their first names, that reads those patterns to rebuild a map.
But chains and forks leave the same fingerprint. A chain from A through B to C and a fork with B in the middle look identical in the data. So from observational data alone, an algorithm can usually narrow things down to a family of maps that fit equally well. That family is called an equivalence class. It's rarely one map.
Even that needs strong assumptions: that no important common cause is missing from the data, and that real effects never cancel each other out by coincidence. Newer methods turn discovery into an optimisation problem, and look impressive on benchmarks. But in 2021, researchers showed that some of that success came from a quirk in how test data were simulated, not from finding causes.
On real farm data, with missing variables and measurement error, a discovered map can change with small changes to the data. What about large language models? They've read much of what's been written about causes, and they can suggest plausible arrows: rainfall affects yield, not the other way round.
In published tests they do well at naming the direction of familiar cause-and-effect pairs. But given formal causal reasoning problems, such as a set of correlations and a question about what follows, they make many mistakes. One paper called them "causal parrots": they repeat causal knowledge from text without reasoning about it.
So use AI as a drafting partner. A discovery algorithm can suggest arrows you hadn't considered; a language model can gather what's been written. Then put the draft in front of experts, test what it predicts, and choose the design. The map still has to earn its arrows. Next, in Module 5: the chain from soil to plate.
Because they leave the same fingerprint. In a chain from A through B to C, and in a fork with B in the middle, A and C move together, and holding B fixed separates them. Only colliders are distinctive. So from observational data alone, an algorithm usually narrows things down to an equivalence class of maps.
In published tests they do well at naming the direction of familiar cause-and-effect pairs, such as rainfall affecting yield. But given formal causal reasoning problems, such as a set of correlations and a question about what follows, they make many mistakes. One paper called them “causal parrots”.
Causal evidence is changing how farming is measured and rewarded. Leave your email and we will tell you when new films, courses and findings are published.
Prefer to read online? Vitagri also writes on Substack. See our privacy policy for how we use your email.