Sonnet 5.5 vs Opus 5.5: Industrial Answers and Output Format
On 250 shared industrial questions, Opus earned 66% strict accuracy and Sonnet 50%. Output-format failures affected both models.
On 250 shared industrial questions, Opus earned 66% strict accuracy and Sonnet 50%. Output-format failures affected both models.
On 487 industrial questions, local Muse Glimmer finished three answers behind cloud-hosted Decision-1, and four after reversing the options.
Microsoft-Decision-1 matched 93.84% of 487 industrial benchmark answers. Five reversed-option runs revealed stable choices and persistent errors.
Gemini 4 Argon scored 42.94% on 170 shared questions. A four-model comparison examined strict answer accuracy at provider defaults.
Across five new runs per model, cross-level agreement marked more accurate subsets—but consistent mistakes remained common.
On simulated machine failures, a trained classifier led the comparison; a simple rule also had a higher score than the tested language models.
Four small local models, an industrial question-answering benchmark, and the difference between correct answers and usable output.
AI selected a smoothing parameter while a formula calculated orders. Every tested condition dampened variance; superiority over a fixed setting was not established.
Fourteen variants, including perfect labels, tested whether better classification could improve the same ordering architecture.
Four models interpreted seasonal and disruption signals, but their ordering results clustered near the formula-only baseline.
A five-label interface produced valid answers on every tested call. It did not make the simulated supply chain more stable.
A formula handled the arithmetic while AI chose the buffer multiplier. All tested model conditions increased variance over a fixed multiplier.
Testing seasonal ordering behaviour on a synthetic Indian automotive demand series—and separating model results from serving reliability.
Every tested rule-based baseline produced both lower order variance and fewer stockouts than every language-model condition.
An exploratory comparison found that business context helped one model and hurt another. All four configurations amplified order variance.