feat(retrieval): add dynamic temporal retriever#54
Merged
Conversation
Introduces a new retriever component to improve handling of temporal queries, specifically for the Bundestag use case. - : A retriever that dynamically applies temporal filters based on keywords detected in the user's query. It uses a to identify 'current' vs. 'historical' queries and filters metadata accordingly. This change also includes significant refactoring of existing components to support this new functionality: - : Refactored to be temporal-aware. It now expands queries with temporal context (e.g., adding '21. Wahlperiode' to a 'current' query) to improve semantic matching. - : Updated to use the to apply temporal filtering at the postprocessing stage, ensuring documents match the query's temporal intent. - : A new configuration concept to centralize the logic and keywords for defining temporal contexts (e.g., 'bundestag.json'). Comprehensive unit tests are added for all new and refactored components to ensure correctness.
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.
Introduces a new retriever component to improve handling of temporal queries, specifically for the Bundestag use case.
This change also includes significant refactoring of existing components to support this new functionality:
: Refactored to be temporal-aware. It now expands queries with temporal context (e.g., adding '21. Wahlperiode' to a 'current' query) to improve semantic matching.
: Updated to use the to apply temporal filtering at the postprocessing stage, ensuring documents match the query's temporal intent.
: A new configuration concept to centralize the logic and keywords for defining temporal contexts (e.g., 'bundestag.json').
Comprehensive unit tests are added for all new and refactored components to ensure correctness.