Chapter 6 of 8
Sampling settings for structured extraction
Structured extraction wants the single most likely continuation at every position, because the output has to parse and there is one right answer per field. A temperature copied from an SDK quickstart buys occasional wrong tokens at exactly the positions where a brace or a field name decides whether the document parses, and a per-position risk of 0.0007 compounds to a four percent document failure rate. This chapter covers which settings an extractor needs, how to classify parse failures before changing anything, and what a second-call repair step is really buying.
Sampling — read the current version at https://daviddominguez.dev/learn/en/sampling/sampling-settings-for-structured-extraction