feat(python): discover actual entity and relationship types from the …#65
Merged
Conversation
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
beinan
approved these changes
Dec 15, 2025
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
2 participants
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.
…table
Currently, the Python-based knowledge graph's QA component accepts the manually created graph config and the real LLM (or Heuristic) extracted entity and relationship types. The two schemas are not necessarily the same and can cause issues in generating and running Cypher queries. For example, the manually created graph config may use
WORK_AT, but the LLM extracted relationship type may beWORK_FOR.This PR addresses the issue by always discovering the actual entity and relationship types first (cache is used to improve performance) and leveraging the manually created graph config as a fallback.