Question

You are building a RAG application over a customer support knowledge base composed of thousands of short FAQ entries. Each entry is a self-contained question paired with a concise answer, and entries are typically 2-4 sentences long. Retrieval accuracy is currently poor because chunks frequently split a question from its answer or merge multiple unrelated FAQs together. Which chunking strategy best fixes this?

Accepted Answer

Treat each FAQ question-and-answer pair as a single chunk, aligning chunk boundaries to the natural document structure.

Answer

Use a fixed-size character chunker of 512 characters with 50-character overlap applied uniformly across the concatenated document.

Answer

Chunk at the sentence level so each individual sentence becomes its own embedding for maximum granularity.

Answer

Merge the entire knowledge base into one large chunk so all context is always available to the retriever.