← Back to Concept Contrast

Concept Contrast Fable

Chunking and parent-child chunking: one is cutting tofu, the other is cutting the tofu while still keeping the original plate of food

Conclusion first:When building a RAG system, chunking and parent-child chunking are written on the same configuration line, and many people think parent-child chunking is just a parameter setting of chunking. Chunking determines how large to cut documents and how to cut them; parent-child chunking preserves the correspondence between the original chunk and the child chunk while cutting, so that retrieval can use the large chunk to locate and the small chunk to answer precisely. Without that layer of correspondence, recall accuracy differs by an order of magnitude.

When building a RAG system, chunking and parent-child chunking are written on the same configuration line, and many people think parent-child chunking is just a parameter setting of chunking. Chunking determines how large to cut documents and how to cut them; parent-child chunking preserves the correspondence between the original chunk and the child chunk while cutting, so that retrieval can use the large chunk to locate and the small chunk to answer precisely. Without that layer of correspondence, recall accuracy differs by an order of magnitude.

Fable

Two numbering methods in the archive

The archive wanted apprentices to quickly look up old cases. At first the whole volume was too thick—finding a single testimony took half a day. So the curator had the files cut into small pieces, each labeled with a number, and lookup became much faster. The apprentice was like taking small pieces from a large platter—easier to swallow.

Trouble followed. An apprentice found a sentence saying "the riverbank has been repaired," but did not know which year, which stretch of river, or who had inspected it. Small pieces are like cut tofu: easy to swallow, but they lose the flavor of the original dish. A fragment looks accurate, but only when put back into the original case does one realize the meaning has changed.

Someone suggested cutting the slices larger. Larger gives enough context, but lookup is slow; smaller gives accurate lookup, but reading is fragmented. The two sides argued for days without resolving it. The first fix just went in circles around the blade thickness and didn't address the relationship between the small slices and the original scroll.

The old librarian switched to parent-child volumes. Small pieces were still used to find clues, like touching a key piece of testimony in a catalog; once a hit was found, the large page or entire parent volume it belonged to was pulled out together, letting the apprentice judge within the original context.

The first version of the father-son volume also had problems. If the father volume took too much, the desk was again piled with paper; if the father volume took too little, the causes and consequences were still unclear. The old librarian redefined the scope by case: testimony included interrogation pages, engineering records included the acceptance sections before and after, and accounts included the same batch of income and expenditure.

Later the archive had two rulers: how fine the small pieces were determined how accurately you could find things; how large the parent volume was determined whether what you retrieved was complete enough to read. Apprentices first used the small pieces to locate, then relied on the parent volume to understand, no longer treating a single isolated sentence as the conclusion of an entire case.

Cutting it into pieces is only finding the needle; bringing the parent volume back too is how you know what garment the needle was stuck in. What the archive truly learned was not to cut more finely, but that searching and understanding are two separate steps.

Later, when new cases entered the archive, the archivist first decided two things: how small a piece to use for the index, and how large a parent volume to provide for reading. The former affected whether something could be found; the latter affected whether it could be judged. Once the two rulers were clearly separated, the files were no longer cut into amnesiac scraps. Later, when archivists looked up a short phrase, they would first ask which volume it belonged to, then decide whether it could be cited.

Chunking

Splitting long documents into smaller passages or text chunks according to a certain strategy, determining chunk size, overlap method, and separation rules, is a foundational preprocessing step for RAG systems.

Parent-child chunking

A specific implementation of chunking: retain larger parent chunks for semantic matching and localization, while maintaining smaller child chunks for returning precise content, with the two linked through an index.

Story Mapping

  • Cut one independent package every five pages: a pure chunking strategy, fragmented retrieval
  • Additionally keep the full version as a positioning anchor: introduce the parent chunk concept
  • Find the summary ID first, then retrieve the chunk: a parent-child chunk retrieval process—parent chunks locate, child chunks answer precisely
  • Loose Tofu vs. Each Block of Tofu with a Dish Label: The core difference between chunking and parent-child chunking is whether there is hierarchical ownership

Falling into RAG system design

When configuring chunking parameters, treat chunk_size and parent_chunk_size as two independent decisions. chunk_size determines the precision of the passage returned to the LLM, while parent_chunk_size determines the scope of semantic matching. First set the parent chunk large enough to capture complete semantics, then set the child chunk small enough to keep answers from being redundant. Tuning only chunk_size means giving up the retrieval precision lever of the parent chunk.

京ICP备2026014272号