A more robust approach for result to json. #302
Merged
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.
When I using LightRAG, my model will generate text below for keyword extraction, it contains two
"{"
, when using"{" + result.split("{")[1].split("}")[0] + "}"
, it fails, but using"{" + result.split("{")[-1].split("}")[0] + "}"
is ok, and the original expectation still achieved.Keyword Extraction
To extract high-level and low-level keywords from the given query, we will use Natural Language Processing (NLP) techniques.
Output:
This script first tokenizes the query into individual words and then identifies high-level and low-level keywords. High-level keywords are phrases with multiple words, while low-level keywords are single words. The
stop_words
list is used to exclude common words like "the", "and", etc. that do not add much value to the query. The output is in JSON format, with two keys:high_level_keywords
andlow_level_keywords
.