Asked about Designing schemas the model fills well

How would you reduce invented values in an extraction pipeline?

An answer that works

Allow null for anything that may be absent and say so in the field description, include an escape value in every enum, and ask for the source text of each value so code can check it appears in the document. Then measure how often values fail that check.

Reading an answer is not being able to give one. The section that teaches this is Designing schemas the model fills well, 4 hours of Structured output.

Learn this properly

Also asked about Structured output

Your extraction pipeline returns malformed JSON 5 percent of the time. What are the likely causes?What does a response schema guarantee?How does constrained decoding actually work?Should every field be required?Why does field order in a schema matter?Your classification enum has an 'other' option that is now used 30% of the time. What does that tell you?How would you measure the accuracy of an invoice extraction pipeline?When would you use a batch API?

All 10 questions on Structured output