Add a separate schema model for LLM structured output#506
Merged
Conversation
NathalieCharbel
approved these changes
Apr 9, 2026
Contributor
NathalieCharbel
left a comment
There was a problem hiding this comment.
LGTM!
I like this new separation of the extracted model from GraphSchema.
stellasia
reviewed
Apr 9, 2026
007830d to
f9f95ca
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Summary
Introduces a lean
GraphSchemaExtractionOutputmodel for schema-from-text structured output (response_format) instead ofGraphSchema, then converts toGraphSchemaviaGraphSchema.from_extraction_outputso the rest of the pipeline is unchanged.Details
Extracted*types + reusedPattern/ConstraintType; sharedNeo4jPropertyTypeNamewithPropertyTypemake_strict_json_schema_for_structured_outputinneo4j_graphrag.utils.json_schema_structured_output(used byGraphSchema.model_json_schemaand the extraction model)validate_extraction_dict_to_graph_schemafor shared validation after extractionWhy
Smaller provider JSON schemas (no root
additional_*, fewer defs) and clearer separation between schema extraction LLM structure output format and runtime pipeline configGraphSchema.It will now be much easier to separate concerns between these two previous roles of
GraphSchema.Type of Change
Complexity
Complexity: Medium
How Has This Been Tested?
Checklist
The following requirements should have been met (depending on the changes in the branch):