Fixes for graph pruning #359
Open
+389
−252
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
|
should we also update this diagram and its description in the docs so we make it clear that the pruner now is a component and executed after the extractor? |
| @@ -24,6 +24,7 @@ A Knowledge Graph (KG) construction pipeline requires a few components (some of | |||
| - **Schema builder**: provide a schema to ground the LLM extracted node and relationship types and obtain an easily navigable KG. Schema can be provided manually or extracted automatically using LLMs. | |||
| - **Lexical graph builder**: build the lexical graph (Document, Chunk and their relationships) (optional). | |||
| - **Entity and relation extractor**: extract relevant entities and relations from the text. | |||
| - **Graph pruner**: clean the graph based on schema. | |||
There was a problem hiding this comment.
shall we also add that it's optional?
There was a problem hiding this comment.
What is optional? The component is not optional, the cleaning is depending on what is defined in the schema, which is what the sentence says, no?
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
Type of Change
Complexity
Complexity:
How Has This Been Tested?
Checklist
The following requirements should have been met (depending on the changes in the branch):