---
title: "Comment by Ahmet Özel on \"Hybrid Search and Reranking: Fixing Retrieval After Vector Search Falls Short\" | Hashnode"
description: "The two-researcher analogy assumes both ranked lists identify the same kind of item. In practice one search leg may return document IDs while the other returns"
url: "https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9/comment/6aed94c5b2cd1143f171a2cd"
---

[Discussion](https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9)

Comment [Hybrid Search and Reranking: Fixing Retrieval After Vector Search Falls Short](https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Nov 6](https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9/comment/6aed94c5b2cd1143f171a2cd)

The two-researcher analogy assumes both ranked lists identify the same kind of item. In practice one search leg may return document IDs while the other returns passage IDs, and RRF cannot recognize agreement between them unless the fusion key is defined consistently.

I would record the ranking unit at each stage and test a document returned by the keyword leg whose relevant passage is returned by the dense leg. Decide explicitly whether fusion happens at passage or document level, then preserve the mapping for the reranker. That makes a high rank in both lists a well-defined claim instead of an artifact of incompatible identifiers.

[Nagappan S](https://hashnode.com/@imkarthik03)

[Nov 9](https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9/comment/6aed94c5b2cd1143f171a2cd#reply-6af1a5b7a83903c56a0414a7)

The post doesn't cover the fusion key, so thanks for raising it. I'd pick one unit for both legs, passage level, and carry the parent document ID as metadata so the reranker and citations can still use it. Your test case is the right one: a document the keyword leg returns whose relevant passage only the dense leg returns. Without a consistent key, a high rank in both lists isn't a well-defined claim.

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[1d ago](https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9/comment/6aed94c5b2cd1143f171a2cd#reply-6afb78694a85fc13205058d7)

Passage-level fusion with parent document IDs gives the reranker and citation layer a consistent item to work with. The remaining choice is how the keyword leg turns a document hit into passage candidates.

I would record that expansion explicitly and retain the matched text location, then test a document whose heading matches the question while its answer lies in a later passage. That shows which passage acquired the keyword evidence and whether the correct passage survives before reranking begins.
