Repository navigation
feat: Add SemanticResolver component for entity resolution using TEI (#10985) - #13627
Closed
tech00exploere wants to merge 9 commits into
Closed
tech00exploere wants to merge 9 commits into
tech00exploere wants to merge 9 commits into
Conversation
Contributor
|
@priyanshuANDcoad is attempting to deploy a commit to the deepset Team on Vercel. A member of the Team first needs to authorize it. |
tech00exploere
force-pushed
the
feat/semantic-resolver-component
branch
from
November 9, 2026 06:50
10b0543 to
417ac42
Compare
…y type normalization
Member
|
Hello, and thanks for contributing. I'm closing this PR based on #10985 (comment). (Additionally, a component based on HF TEI should live in Core Integrations) |
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
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.
Related Issues
SemanticResolvercomponent #10985Proposed Changes
Adds a new
SemanticResolvercomponent underhaystack/components/preprocessors/to identify and merge semantically equivalent entity names in document metadata using the Hugging Face Text Embeddings Inference (TEI)/similarityendpoint.The component includes:
/similarityendpoint to compare entity names in batches. Supports authentication through Haystack'sSecrettype.entity_type(group_by_type=True), preventing entities from different categories from being merged.most_frequent,shortest,longest, andfirststrategies to choose a canonical name for each cluster.Documentinstances without modifying the input documents. Preserves document IDs, blobs, embeddings, and unrelated metadata.original_<entity_key>, preserving previously collected aliases across repeated runs.run) and asynchronous (run_async) execution, context management, and component serialization/deserialization throughto_dictandfrom_dict.docs-website/and a Reno release note.How did you test it?
Added 30 unit and integration tests in
test/components/preprocessors/test_semantic_resolver.py, covering:Checks performed:
ruff check: passed.ruff format: passed.mypy: passed with no errors.Notes for the reviewer
group_by_type.Checklist
feat:) in the PR title.AI disclosure: ### AI Disclosure
I investigated and implemented this feature myself and used an ai assistant only to help investigate the issue, explore possible approaches, and discuss design considerations. The implementation, tests, and changes in this pr are my own work.