-
Notifications
You must be signed in to change notification settings - Fork 102
Automatic schema extraction from text #331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
NathalieCharbel
merged 37 commits into
neo4j:main
from
NathalieCharbel:automatic-schema-extraction-from-text
May 14, 2025
Merged
Automatic schema extraction from text #331
NathalieCharbel
merged 37 commits into
neo4j:main
from
NathalieCharbel:automatic-schema-extraction-from-text
May 14, 2025
Conversation
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
stellasia
reviewed
Apr 29, 2025
src/neo4j_graphrag/experimental/pipeline/config/template_pipeline/simple_kg_builder.py
Outdated
Show resolved
Hide resolved
src/neo4j_graphrag/experimental/pipeline/config/template_pipeline/simple_kg_builder.py
Outdated
Show resolved
Hide resolved
src/neo4j_graphrag/experimental/pipeline/config/template_pipeline/simple_kg_builder.py
Outdated
Show resolved
Hide resolved
src/neo4j_graphrag/experimental/pipeline/config/template_pipeline/simple_kg_builder.py
Outdated
Show resolved
Hide resolved
src/neo4j_graphrag/experimental/pipeline/config/template_pipeline/simple_kg_builder.py
Outdated
Show resolved
Hide resolved
stellasia
reviewed
May 6, 2025
stellasia
reviewed
May 11, 2025
src/neo4j_graphrag/experimental/pipeline/config/template_pipeline/simple_kg_builder.py
Outdated
Show resolved
Hide resolved
src/neo4j_graphrag/experimental/pipeline/config/template_pipeline/simple_kg_builder.py
Show resolved
Hide resolved
stellasia
reviewed
May 13, 2025
examples/automatic_schema_extraction/simple_kg_pipeline_schema_from_pdf.py
Outdated
Show resolved
Hide resolved
src/neo4j_graphrag/experimental/pipeline/config/template_pipeline/simple_kg_builder.py
Show resolved
Hide resolved
stellasia
approved these changes
May 13, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @NathalieCharbel , amazing to have this feature in! 👩🚀
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
This PR adds support for automatic schema extraction using LLMs:
SchemaFromText
component that uses LLM to analyse text and automatically extract a guiding schema, which can be used later in entity/relation extractionschema
parameter in SimpleKGPipeline that replaces deprecated individual schema parameters (i.e.,entities
,relations
,potential_schema
), which can be now provided manually or from the output of LLM (asSchemaConfig
object)SimpleKGPipeline
when no schema is providedauto_schema_extraction
flag (so far added toSimpleKGPipelineConfig
only i.e., configurable from config files)SchemaConfig
Class)Type of Change
Complexity
Medium
How Has This Been Tested?
Checklist
The following requirements should have been met (depending on the changes in the branch):