Chapter 2
The same prompt can produce different answers
In traditional finance software, identical inputs always generate identical outputs.
If you refresh a spreadsheet containing an interest rate formula, the cell never displays 5.2% on Monday and 5.4% on Tuesday. If your accounting system runs an SQL query on last year's ledger, the total revenue figure remains identical to the penny across ten thousand consecutive runs.
When analysts move from financial software to large language models, this foundational certainty shatters.
You can paste the exact same earnings release into the exact same prompt window, click submit three times, and receive three noticeably different summaries. Most of the time, the wording merely shifts. But occasionally, a crucial financial digit drifts: an operating margin changes from 15.0% to 14.8%, or a bullet point disappears entirely.
This run-to-run variation is not a software crash. It is an observed mathematical consequence of how the machine selects its words.
Sampling draws candidate tokens from a probability bag
In Chapter 1, we learned that a language model computes the conditional probability of every possible next token. But computing probabilities is only half the job. The model must actually choose which token to emit.
How does the machine make that choice?
Think of the candidate tokens as poker chips inside a bag.
When the model finishes reading the phrase Acme reported fourth-quarter revenue of, its neural network calculates a probability distribution across its entire vocabulary:
- The exact number from your text ($4,280) gets 82 chips.
- A rounded approximation ($4,200) gets 11 chips.
- A transposed number ($4,820) gets 5 chips.
- Other candidate tokens share the remaining 2 chips.
To select the next token, the harness reaches into the bag and draws a single chip at random.
Eighty-two times out of a hundred, the machine draws the correct number. But eighteen times out of a hundred, it draws an alternative chip. Once that alternative token lands on the page, the entire mathematical context shifts. Every subsequent token is now conditioned on that altered choice.
The dial that controls this selection process is called temperature:
When temperature is high, the neck of the bag widens. Unlikely tokens receive more chances to be drawn, making the writing colorful and varied. When temperature is low, the top-ranked token dominates.
Zero temperature narrows the draw but does not guarantee identical runs
When financial analysts first discover temperature, their immediate instinct is simple: Turn the dial to zero.
Setting temperature to zero instructs the model to use greedy decoding: always select the single candidate token with the highest mathematical probability. Never draw from the rest of the bag.
For simple qualitative drafting, greedy decoding reduces variation. But in enterprise environments, leaders make a dangerous assumption: they assume that zero temperature makes an LLM as deterministic as an SQL database.
It does not.
In production architectures, identical prompts sent with zero temperature still exhibit run-to-run drift for three technical reasons:
- Floating-point non-determinism across parallel chips: Frontier models run across clusters of dozens of specialized graphics processors. Because floating-point addition in high-speed parallel silicon is non-associative, minor variations in thread execution order slightly alter the final logits. When two candidate tokens sit within 0.0001% probability of each other, microscopic rounding noise flips the winner.
- Dynamic batching on server clusters: Enterprise API endpoints group concurrent queries from different users into dynamic computation batches to maximize throughput. Changing batch dimensions alters GPU matrix scheduling, shifting sub-word probability boundaries.
- Silent model updates and weight quantization: Frontier model providers continually update internal routing weights, system prompts, and safety filters without incrementing version labels. A prompt run on Friday morning may run against different model artifacts than the identical prompt run on Monday afternoon.
In business and finance, you cannot eliminate variance by configuring a single software parameter. You must design workflows that verify outputs regardless of variation.
Running scenario: The specimen number shifts on a second extraction run
Let us re-run the exact extraction prompt from Chapter 1 on Acme Industrial Technologies to observe sampling variance in practice.
You paste the identical press release excerpt into the prompt box and submit it with standard sampling parameters:
Document:
"Acme Industrial Technologies (NYSE: AIT) delivered a resilient finish to the fiscal year despite persistent supply chain friction in European markets. For the fourth quarter ended December 31, consolidated revenue reached $4,280 million, a 6% increase compared to $4,038 million in the prior-year period. Operating income expanded to $640 million from $595 million, reflecting price realization across heavy equipment lines. Full-year backlogs closed at record levels, though management noted cautious capital expenditure trends among regional industrial customers entering the first quarter."
Instructions:
Summarize the fourth-quarter performance for Acme Industrial Technologies.
State the total revenue and the year-over-year growth rate.
Use two concise sentences.
On your first run in Chapter 1, the model returned:
Acme Industrial Technologies reported fourth-quarter revenue of $4,280 million, representing a 6% increase year-over-year. Operating income reached $640 million, supported by price realization across heavy equipment lines.
On this second run, a different sampling path unfolds:
In the fourth quarter, Acme Industrial Technologies achieved consolidated revenue of $4,200 million, reflecting 6% year-over-year top-line growth. Operating income expanded to $640 million, supported by price realization across heavy equipment lines.
Look closely at what happened.
The prose remains polished and authoritative. The six percent growth rate and the $640 million operating profit survived. But the headline revenue figure drifted from $4,280 million to $4,200 million. A lower-probability token ($4,200) was selected, rounding away $80 million in actual sales.
An analyst reading casually would never notice the error. The text reads with complete grammatical confidence.
How do you preserve conversational context across follow-up queries without state?
Here is the problem to think about before you move to the next chapter: what happens when you continue working with this summary? When you ask a follow-up question about Acme's operating margin, how does the model know what you discussed three seconds ago? If the machine has amnesia between calls, how does a chat session hold together?
The Leader's View: Treat reproducibility as an archival problem, not a configuration setting
When managing teams deploying AI in valuation, risk modeling, or regulatory compliance, leaders must establish clear policies around run-to-run variance.
The common executive error is relying on vendor promises of "deterministic mode." A vendor who claims their LLM is fully deterministic is either describing a toy prototype or obscuring production cluster mechanics.
Operating rules to mandate
- Snapshot raw payloads and model identifiers: Because you cannot guarantee identical re-generation next month, treat every LLM output as a perishable artifact. For any analysis supporting public filings, investment decisions, or audit memos, record the cryptographic hash (SHA-256) of the input prompt, the exact model release string, the temperature setting, and the complete raw output.
- Decouple numerical extraction from freeform text generation: Never allow a generative model to perform final quantitative extraction on financial filings without a secondary deterministic check. When extracting financial statements, use structured extraction harnesses that cross-verify figures against original PDF text coordinates.
- Benchmark variance on internal document suites: Do not rely on vendor benchmark scores published in research papers. Run internal Monte Carlo evaluations: submit your firm's actual credit memos or 10-K filings twenty times at temperature 0.2 and measure the exact rate of numerical mutation across runs.
Questions to put to a vendor
- Does your API guarantee bitwise reproducible outputs across multi-tenant GPU clusters when temperature is set to zero? If not, what is the measured mutation rate on numerical tables?
- When you update safety layers, system prompts, or model weights, do you pin immutable version identifiers so our historical runs remain auditable?
Zoom-out: Distinguish fluent phrasing from factual comprehension
The phenomenon of run-to-run variance exposes a philosophical truth that every business leader must confront: grammatical fluency is not factual understanding.
Human beings evolved to associate verbal fluency with intelligence and competence. When an analyst presents a clear, articulate, grammatically impeccable summary of an industrial balance sheet, our instinct is to assume they comprehend the underlying corporate balance sheet.
A large language model possesses verbal fluency without a shred of comprehension.
The model is a statistical mirror of human writing. It weaves standard financial vocabulary, cadence, and tone with astonishing elegance because its training corpus contains millions of professional equity research reports. It knows that the word revenue frequently precedes grew by, and that operating profit pairs naturally with margin expansion.
When the model outputs $4,200 million instead of $4,280 million, it experiences no cognitive dissonance. It has no mental picture of Acme's factories, no concept of what eighty million dollars represents, and no obligation to the truth. It simply completed a statistical chain of tokens.
In corporate life, the danger of generative AI is not that it sounds uneducated. The danger is that it sounds like an experienced vice president even when it is completely wrong. True institutional defense begins when leaders stop treating fluent phrasing as proof of factual comprehension.