Bridgewater trained a model just for triaging financial information — 84.7% accuracy, methodology public
- Thinking Machines Lab, together with AIA Labs at Bridgewater, used their in-house fine-tuning platform Tinker to train a custom model specialized in financial information triage.
- Top frontier models (Gemini, Claude, GPT families) using simple prompts on 6 financial triage tasks averaged only about 50% accuracy. After heavy prompt optimization, the best reached 78.2% — still short of the 80% credibility threshold investors require.
- The training data initially came from non-expert labelers and was riddled with errors. The team designed a scheme where only "disagreement" samples — where the model's judgment didn't match the label — went to expert review, while the rest were kept as-is, keeping labeling costs down.
- Starting from the open-source Qwen3-235B base model, standard GRPO reinforcement learning fine-tuning pushed accuracy to 73.48%. Stacking on interleaved batch training, the CISPO asymmetric clipping loss, and online policy distillation with dynamic teacher promotion brought it to 84.66%.
- The final model hit 84.7% accuracy — a 29.8% lower error rate than the best frontier model tested (78.2%), with per-task inference cost at just 1/13.8 that of the corresponding frontier model.
News an investment manager judges in a second — AI can only guess
Thinking Machines Lab and Bridgewater's AIA Labs jointly published a post detailing how they used the in-house fine-tuning platform Tinker to train a financial information triage model, along with the results.
What they set out to automate isn't writing research reports — it's the "information triage" investment managers do over and over, every day: pulling out what's actually worth reading from a flood of news, research reports, company filings, and emails. The reading itself isn't hard; what's hard is that layer of up-close judgment, which eats up huge amounts of time. The team wanted to see: can this work be handed off to a model?
Six "small things" investment managers do every day
These six things are second nature to investment managers — judged in a second. But the moment you have to explain "how exactly did I decide that," people get stuck — which is precisely why they're hard to teach an AI. The team broke them out one by one into a benchmark.
The first three are classification tasks (evaluated on accuracy + F1 score), the last three are localization tasks (evaluated on exact-match accuracy). The original post notes that internally there are many more tasks like these, and the pattern holds throughout: frontier models generally underperform their own trained models on this kind of work.
Both touch on politics and finance — why is one relevant and the other not
Take the "financial article relevance" task as a real example. The two headlines below both brush against geopolitics and finance — yet for a macro investor, one is worth reading and the other should be swiped away without a second thought. Take a guess which one's relevant.
Reveal: which is relevant, and why
B is relevant, A isn't. In context, the Greenland headline reads more like a political posture the market won't take seriously; the China tariff threat, on the other hand, directly triggered the S&P 500's worst single-day drop in weeks — a hard, unmistakable market signal. Yet both touch geopolitics and finance at once, so keyword matching alone can't tell them apart — and that's exactly where models trip up. This kind of judgment is about investment context, not surface-level word matching.
Tuning prompts every which way, AI still caps out at 78.2%
The team first took the cheapest route: rescuing the results through prompt engineering. Experts rewrote the instructions to reflect real task descriptions, and even redefined the tasks — for instance, splitting article classification from "relevant / not relevant" into three categories: "relevant and interesting," "relevant but uninteresting," and "not relevant," since a minor IPO news item is technically financially relevant but lacks the macro significance a macro investor cares about.
Prompting pulled accuracy from coin-flip level up to the 70s, but hit a ceiling beyond that — automated prompt optimization couldn't squeeze out any more headroom. The original post also notes: "more expensive doesn't mean more accurate." GPT 5.4 costs 43% more than 5.2, yet only shows a small accuracy gain — meaning newer models aren't making much progress on this kind of task, especially per dollar spent.
Optimized accuracy / F1 by frontier model (original data)
| Frontier model (best prompt) | Accuracy | Positive-class F1 |
|---|---|---|
| Model family one | ~47.2% | 77.2% |
| Model two | 50.1% | 74.3% |
| Model three | 47.2% | 75.8% |
| Model four (best) | 48.5% | 78.2% |
| Model five | 45.6% | 78.0% |
Note: F1 is averaged across the 3 classification tasks; accuracy is averaged across all 6 tasks. Per the original post, the best frontier model's accuracy ceiling is 78.2% — this is also the benchmark the custom model is later compared against.
The labeled data itself was wrong: how to route only truly hard samples to experts
Once prompting hit its ceiling, the team turned to fine-tuning. But the first obstacle wasn't training — it was data: these judgments only have value if they've passed through an investment expert's eyes. The labels the team initially bought from a vendor were non-expert, and training on them still produced a poor model. Only when they looked through the model's reasoning traces did they discover the labels in the dataset were often simply wrong.
Having experts relabel everything was too expensive. So the team came up with a clever workaround: let the model itself flag "suspicious" samples, and only send those to experts. The logic is straightforward — if a sample doesn't even match its own training-set label, either the question is genuinely hard, or the original label is wrong. Either way, it's worth an expert's eyes.
This way, expert labor gets spent only on genuinely disputed samples, while the rest stays as-is — cleaning the data while keeping costs in check. The final evaluation, meanwhile, runs on a completely independent held-out set that never went through the cleaning process, avoiding any self-grading bias.
Three combined moves push accuracy from 73% to 84.7%
With clean data, training began. The team picked Qwen3-235B — the most thoroughly studied open-source model in academia — as the base, and ran all training on Tinker, with no need to manage GPU infrastructure themselves. Step one, standard GRPO reinforcement learning fine-tuning, laid the foundation: accuracy jumped from the base model's 44.8% to 73.48% — still short of the 80% threshold. What actually pushed it over the line were three improvements stacked on top.
GRPO is a reinforcement learning method that doesn't require training a separate "judge model": the model produces a batch of candidate answers for the same question, compares them against each other to see which is closest to the correct answer, and the better ones get reinforced going forward. Like a group of people solving the same problem — instead of a teacher grading them, they compare answers against each other to see who got closer.
The staircase shows three real data points from the original post: base 44.8% → GRPO 73.48% → full recipe 84.66%. The 11-point jump in the middle comes from the combination of the three improvements below.
The percentages below each come from an "ablation experiment": remove one item from the full recipe and see how much accuracy drops. These numbers don't simply add up — each is essential; drop any one and performance falls noticeably.
Full ablation data (drop one item, see how much it costs)
| Training configuration | Average accuracy | Positive-class F1 |
|---|---|---|
| Qwen base | 44.8% | 55.24% |
| Qwen + GRPO | 73.48% | 88.95% |
| Qwen + full recipe | 84.66% | 92.99% |
| − Interleaved batch training | 72.18% | 89.01% |
| − CISPO asymmetric clipping | 74.56% | 90.64% |
| − Online policy distillation | 72.39% | 87.93% |
| − Dynamic teacher promotion (fixed base model as teacher instead) | 81.55% | 89.41% |
What CISPO and "online policy distillation" actually do
Of the three moves above, CISPO and online policy distillation have the most intimidating names. You don't need to understand reinforcement learning — what they're solving is really the same basic problem: don't let the model overshoot or drift, and give it a solid teacher to learn from.
It governs "how much the model is allowed to change in a single step." It applies different tolerances to "learning in the right direction" versus "learning in the wrong direction" — like correcting a student: let them take big strides toward the right answer, but the moment they start drifting toward a wrong one, pull the reins in tight. That way the model neither overshoots nor becomes too timid to move.
Online policy distillation + dynamic teacher promotion
The student model practices on its own while also referencing the answer distribution of a "teacher model" — drifting too far from the teacher gets penalized (the original post uses a penalty term: the bigger the gap between student and teacher, the more the reward is docked). The key is that the teacher isn't static: every 20 steps, the system checks accuracy on the validation set, and the moment the student sets a new high, the student itself is promoted to be the new teacher — never regressing by keeping a weaker model in the teaching role.
Like a regular apprenticeship review: the moment the apprentice's skill surpasses the current master's, the master's role is handed to that apprentice, and it's now "a stronger version of themselves" teaching the next stage. This step (dynamic teacher promotion) adds 3.1% over using a fixed base model as teacher.
Error rate down nearly 30%, inference cost cut to 1/14
With all the improvements stacked together, the custom model raised average accuracy from the best frontier model's 78.2% to 84.7% — a level the team considers good enough for everyday use. The bigger savings are in cost: with a far smaller model footprint, per-task inference cost drops to just 1/13.8 that of the corresponding frontier model.
The original post says this conclusion holds well beyond the 6 tasks made public here — the pattern is consistent across a large number of similar internal tasks. The methodology also isn't tied to finance: a workflow of "route hard samples via model disagreement, have experts clean the data, then reinforcement-learning fine-tune" is, in the authors' view, applicable to other organizations' own specific judgment tasks. They call this "differentiated intelligence": custom models tuned to an organization's specific needs outperforming general frontier models on their own work.
Our results show the possibility of a future of differentiated intelligence, where custom models tuned to specific organizational needs outperform frontier models. Thinking Machines Lab (with Bridgewater AIA Labs), "Learning to Replicate Expert Judgment in Financial Tasks," June 2026
An entry-level investing task — sorting financial news — stumps even the strongest general-purpose AI at a coin flip. A specially-tuned small model hits 84.7%.
Bridgewater partnered with Thinking Machines, fine-tuning an open-source model on expert-labeled data: one illustrated page on how it beat frontier AI — and did it fourteen times cheaper.
↓ Read the whole thing in one page · includes an animated chart
Financial information triage is what an investment manager does every day: pulling out what's actually worth spending time on from a flood of news, research reports, company filings, and emails. The reading itself isn't hard; the hard part is that layer of judgment — which item matters, which is noise.
✘ But can't judge which one is actually worth an investment manager's time
Across six such triage tasks, Gemini, Claude, and the GPT family tackling it directly averaged only about 50% accuracy — basically a coin flip. The hard part: "relevant" isn't the same as "meaningful." A Greenland political story and a China-tariffs story both touch on politics and finance, but only the latter triggers a stock market crash — telling them apart takes investment judgment, not keyword matching.
The team first took the cheapest route: tuning prompts (instructions written for the AI) on general-purpose large models as hard as they could. But no matter how much they optimized, the best still capped out at 78.2% — short of the 80% credibility threshold investors require. So they switched tactics: use expert-labeled data to fine-tune (retrain the model on task-specific data) a custom small model.
No amount of optimization gets past the ceiling — still 1.8 points short of the 80% threshold; pricier new models aren't more accurate either.
Trained specifically for this one job, accuracy clears the threshold, and each run costs just 1/14th the compute of a frontier model.
How does a smaller open-source model beat the strongest large model (the "frontier model," i.e. the most advanced general-purpose model)? Not by being smarter — but through two moves: clean up the data first, then get the training recipe right.
Put those two moves together as a pipeline and it clicks. Follow along with a scenario: XiaoHu has a thousand news articles, cheaply outsourced labeling has plenty of mislabels mixed in, and training directly on that just teaches the model to learn the mistakes.
The official figure is "cost down 13.8×." In plain terms: to triage the same batch of documents, a frontier model's inference bill runs about fourteen times what this custom model costs.
Which one
matters?
probably…relevant?
average correct
coin flip
optimize again and again…
this has to work!
1.8 points short, hits a wall
this is the ceiling.
costs too much — but
amateurs mislabel!
clean up only the
truly hard sliver.
fine-tune through trial and error.
and the model can learn.
learned XiaoHu's judgment.
1× cost
it was a small model
tuned for one specific job.
Members can copy or download the full Markdown, and let their AI subscribe and ask.
Found this useful? Leave your email — every new explainer, the moment it's out. Unsubscribe anytime.