---
title: "Comment by Kartik N V J K on \"Why Forced JSON Output Is Always Valid and Sometimes Wrong\" | Hashnode"
description: "Those blurry scan numbers made this click for me. 15% of the probability on the three legal values, and high still comes out 40% of the time looking exactly lik"
url: "https://hashnode.com/posts/why-forced-json-output-is-always-valid-and-sometimes-wrong/6adcc7bb3afe81e3e633f8aa/comment/6adf3f2df2d63d3f7ac401fb"
---

[Discussion](https://hashnode.com/posts/why-forced-json-output-is-always-valid-and-sometimes-wrong/6adcc7bb3afe81e3e633f8aa)

Comment [Why Forced JSON Output Is Always Valid and Sometimes Wrong](https://hashnode.com/posts/why-forced-json-output-is-always-valid-and-sometimes-wrong/6adcc7bb3afe81e3e633f8aa)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Oct 26](https://hashnode.com/posts/why-forced-json-output-is-always-valid-and-sometimes-wrong/6adcc7bb3afe81e3e633f8aa/comment/6adf3f2df2d63d3f7ac401fb)

Those blurry scan numbers made this click for me. 15% of the probability on the three legal values, and high still comes out 40% of the time looking exactly like a confident answer. In my extraction evals I'd also split the test set by input quality, since forced picks on bad scans can hide inside a healthy average the same way one bad schema does.