Click any words you think contain an error. Click again to unmark.
The query path forgets the 'query:' prefix that E5 models were trained to expect, projecting queries into the wrong region of vector space and silently dropping recall.
Imagine two postal services that both deliver mail, but each requires a sticker on the front of the envelope. One sticker says 'Outgoing', the other says 'Incoming'. The post office uses those stickers to sort. If you forget the sticker, the envelope still leaves the office and still gets dropped at addresses. But it ends up at the wrong houses, because the sorter could not tell which pile it belonged to. That is what is happening here. The docs went out with the right sticker, the queries went out bare, and the matches landed in a slightly different neighborhood.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
A missing query prefix is the classic embedding pipeline bug in production code. The code has two functions and one missing prefix. Nothing errors, and the quiet recall drop survives QA.
Isolating the defect
Read the two paths side by side
The index path:
texts = [f'passage: {d.text}' for d in docs]
vecs = embed_model.encode(texts, normalize_embeddings=True)
The query path:
q_vec = embed_model.encode(query, normalize_embeddings=True)
The asymmetry is the bug. The index side wraps each document with 'passage: '. The query side encodes the raw query string. The vector DB call after each is fine. The encoder call after each runs to completion.
What the diff should look like
The correct query path mirrors the index path:
q_vec = embed_model.encode(f'query: {query}', normalize_embeddings=True)
The fix is one line. A six-month deploy without it routes tens of millions of query vectors incorrectly.
Situations where this technique stops working.
2–4 min · Everything important, quickly.
Real products, models, and research that use this idea.
- multilingual-e5-large (intfloat) was trained with query: and passage: prefixes; leaving them off degrades performance.
- E5-large-v2 (intfloat) uses the same two-prefix contract; e5-mistral-7b-instruct instead puts a task instruction on the query side only.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow would you detect this bug if you cannot afford a labeled relevance set?
Sample 200 queries and their top-1 results before and after adding the prefix, score whether the top-1 changed, and inspect a stratified sample. A large flip rate with no obvious win is the signal.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Asserting the code is fine because it runs and returns results. Silent recall drops are the signature of a prefix mismatch, not a thrown error.
60 second bullets to scan on the way to the call.
Which embedding model families require query: and passage: prefixes
Why a missing prefix produces a silent recall drop, not an error
Primary sources. Browse if you want the original framing.
Same topic, related formats. Practice these next.