Equation 2 · Building Production RAG: An Advanced Technical Guide
What does this equation mean?
Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.
This equation states an equality: the expressions on both sides have the same value under the article’s assumptions. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.
Read it piece by piece
Symbol s_hybrid
ybrid is part of the quantity the equation computes from the expression on the right.
Symbol d
d is an argument of the function-like quantity on the left; its role is set by that function’s stated inputs.
Symbol hats_dense
hatense is one of the signed contributions combined to compute the quantity on the left.
Symbol hats_sparse
hatparse is one of the signed contributions combined to compute the quantity on the left.
=
The expressions on both sides represent the same quantity under the stated assumptions.
See an illustrated explanation →subscript
The lower label selects a particular version, component, or indexed member of the quantity. For example, x₀ and xₜ can be values at different positions.
How to interpret it
Read it with the definitions, units, and assumptions supplied by the article.
What the article says around this equation
The fix is hybrid retrieval: combine a lexical score, which is exact-match strong and semantically blind, with a dense score, which is semantically strong and exact-match weak. The complication is that the two scores are not on comparable scales. Pinecone’s documentation states the problem directly: dense vectors scored by inner product against unit-normalized embeddings fall roughly in the range [-1, 1] , while BM25-style sparse scores are unbounded positive values that grow with term frequency, document length, and vocabulary rarity, so that “without explicit weighting, the sparse component dominates the combined score” [ 4 ] . The documented fix is a convex combination of normalized…
Read the full surrounding passage
The fix is hybrid retrieval: combine a lexical score, which is exact-match strong and semantically blind, with a dense score, which is semantically strong and exact-match weak. The complication is that the two scores are not on comparable scales. Pinecone’s documentation states the problem directly: dense vectors scored by inner product against unit-normalized embeddings fall roughly in the range [-1, 1] , while BM25-style sparse scores are unbounded positive values that grow with term frequency, document length, and vocabulary rarity, so that “without explicit weighting, the sparse component dominates the combined score” [ 4 ] . The documented fix is a convex combination of normalized scores, governed by a single weighting parameter: . where the hats denote scores each rescaled onto a comparable range before combination. At = 1 the ranking is purely semantic; at = 0 it collapses to lexical search; = 0.5 weights the two signals equally.
Sources cited in the surrounding passage
These citations give research context. Read each source to check which claims it supports.
Return to Building Production RAG: An Advanced Technical Guide