Chunks split tables and lose their headers. What do you tune?
Why B is the answer
The chunking strategy
Chunking should follow document structure, so that meaning stays together.
In detail
- Chunks should keep tables and headers together.
- Inspect real chunks.
Use case
An illustrative scenario, not a real incident.
Tables are split from their headers, so numbers lose their meaning. A better chunking strategy keeps them whole.
See it in different ways
flowchart TD
A["Poor answers"] --> B{"Right chunks retrieved?"}
B -->|No| C["Tune chunking, embeddings and search"]
B -->|Yes| D["Tune the prompt or model"]stateDiagram-v2 [*] --> CheckRetrieval CheckRetrieval --> TuneChunks: wrong chunks CheckRetrieval --> TunePrompt: right chunks, poor answers TunePrompt --> FineTune: style still not met TuneChunks --> [*] FineTune --> [*]
flowchart LR S0["Find split tables"] --> S1["Change the strategy"] --> S2["Re-index"] --> S3["Re-evaluate"]
Key point: Tune chunking for your documents.
Why the other options are wrong
- A. The number of replicas
- Replicas add capacity.
- C. The deployment region
- Region has no effect on chunks.
- D. The model's temperature
- Temperature has no effect on chunks.