Large language models have quietly become research instruments. They read and code open-ended survey answers. They sort news articles into topics. They simulate how people might respond to a policy. They classify thousands of social media posts in an afternoon. In political science and social science departments, using an LLM as a measurement tool has gone from a novelty to a normal part of the workflow.
But there is a catch, and it is a big one. When a machine gives you a slightly different answer every time you ask the same question, the old rules of scientific proof start to bend. That is the heart of a fast-growing body of work on replicability, reproducibility, and robustness in social science research that relies on large language models.
The short version: the tools are powerful, the results are often real, but the trust framework around them is not yet built. And that gap has lessons far beyond the university, for any business that uses an AI model to make a decision it may later have to defend.
Before we go further, let's untangle the vocabulary. These three terms get used loosely, but in a research setting they mean different things.
Can someone else run the same study again and get the same result? That is replicability. In the LLM world, this is harder than it sounds. The same prompt, sent twice, can produce two different outputs. Ask a model to sort 500 comments into "positive," "negative," and "neutral," and the edges of those categories can shift from run to run.
Can another team, working from your notes and your data, rebuild what you did? That means they need your prompts, your settings, your model version, the date you ran it, and the exact way you cleaned the output. Most published social science papers that use LLMs do not yet include all of that. Without it, "reproducing" the study is guesswork.
Does the finding survive small changes? If you reword the prompt, swap the order of the answer choices, change the temperature, or run the classification on a different day, does your headline conclusion still hold? If a single word change flips your result, you did not measure the thing you thought you measured.
Put together, these three checks answer one question: can we trust this number?
Traditional statistical software is boring in the best possible way. Run the same script on the same data, and you get the same output. Forever. LLMs are not like that, and there are several reasons why.
Many models add a small amount of randomness to their output so they do not sound robotic. That randomness is a feature for a chatbot and a headache for a researcher. Even at the lowest settings, results can drift.
Change "classify this as liberal or conservative" to "which ideology does this text lean toward," and you may get a different coding pattern. Add an example, remove an example, or reorder the label options, and the results move. A prompt is not a survey instrument that has been tested for years. It is often written in one afternoon.
Commercial models get updated, retuned, and sometimes retired. A study run in one month may not be repeatable the next, even with identical inputs. The tool itself is a moving target, and that breaks the basic assumption that a method stays still long enough to be checked.
Most leading models are closed. Researchers cannot inspect the training data, the weights, or the exact version history. That makes it hard to say whether a change in results came from a real shift in the world or a quiet update on the provider's side.
LLMs produce fluent, confident text. A label reads "negative" with no error bar, no confidence score, and no hint of hesitation. Researchers can mistake that fluency for accuracy, a trap that also catches business teams reading AI-generated reports.
Social science already went through a painful reckoning over studies that could not be repeated. The response was a set of reforms: pre-register your hypotheses, share your data, share your code, report what did not work.
LLMs arrived after those reforms and largely sidestep them. There is no standard way to cite a model version. There is no shared format for archiving prompts. There is no accepted test for whether an LLM-based measure is stable. Each lab invents its own approach.
This is not a small bookkeeping issue. It changes what a published finding means. If two careful teams study the same question with the same model and reach opposite conclusions because their prompts differed slightly, the literature stops accumulating knowledge and starts accumulating noise.
The pressure to fix this will not come only from academia. It will come from courts, regulators, auditors, and customers. Once an AI system is used to score a loan application, screen a job candidate, or flag a piece of content, someone will eventually ask: show me that it works the same way every time.
Here is where the research agenda points.
Expect "model cards" and version logs to become as normal as a version number on a software release. Any serious AI deployment will need a record of which model, which settings, and which prompt produced which decision.
Today, prompt writing is craft. Tomorrow, prompts will be tested, validated, and reported the way survey questions are. Teams will run a prompt through many variations to check the result holds.
Before trusting an LLM-based measure, you will run it repeatedly and see how much the answer wobbles. If the wobble is bigger than the effect you are studying, you have a problem, and you will know it before you publish or ship.
When you cannot inspect a closed model or freeze its version, some researchers will switch to models they can download and pin. That gives up some raw capability in exchange for control. For regulated industries, the trade may be worth it.
LLM output will increasingly be paired with human review, and that review will need to be logged, sampled, and measured, not just described as "a researcher reviewed the results."
If you run a team that uses LLMs for anything that matters, the three R's translate directly into operational advice.
There is a temptation to read this as a story about AI's limits. That would miss the point. The push for replicability and robustness is a sign of a field maturing. Nobody demands stability testing from a toy. They demand it from a tool people rely on.
The real shift is philosophical. For years, the question about AI was "can it do the task?" Increasingly, the question is "can we prove it does the task the same way twice, for reasons we understand, and that it keeps doing so after the next update?" That is a harder question, and a more useful one.
Social science is asking it early, in public, with the rigor of peer review behind it. The answers it produces, about how to version models, how to archive prompts, how to test whether a finding is real or an artifact of one phrasing on one Tuesday, will not stay in the journals. They will become the operating manual for every organization that puts an LLM in the decision path.
The models will keep getting better. What will decide whether they are trusted is something less glamorous: whether we can show our work.