A retrieval pipeline embeds 3,000-token passages with an encoder whose input limit is 512 tokens. Important details near passage ends are missing from search. What is the best first fix?

Published
  1. Split passages into meaningful units that fit the encoder limit and re-embed them.
  2. Lower the retrieval timeout to discard more candidates.
  3. Rename the stored vector column.
  4. Increase only the answer generator's output length.

Comments — 0