Structured output

Start with the component that will consume the result. Define the keys, types, allowed values, and meaning of an unknown value before asking a model to populate them. Clear representation choices prevent downstream code from guessing whether different phrases refer to the same category.

Read the structured output guide to connect prompts with validation. Test structure and meaning separately. A valid object can still contain an unsupported name, an inconsistent date, or a source identifier that does not exist in the supplied material.

The LLM contract guide explains how to preserve schemas and evaluation cases together. Include incomplete input and borderline classifications in your examples. Make the application's recovery path explicit when the response is refused, incomplete, or structurally valid but unsuitable for the next step.