Docs: Updated Title chunker references (#14483)

### What problem does this PR solve?

Updated Title chunker references

### Type of change

- [x] Documentation Update
This commit is contained in:
writinwaters
2026-04-29 19:37:24 +08:00
committed by GitHub
parent 261be81127
commit 9280c64518
4 changed files with 91 additions and 11 deletions

View File

@@ -23,7 +23,30 @@ Placing a **Title chunker** after a **Token chunker** is invalid and will cause
## Configurations
### Hierarchy
### Hierarchy or Group
Select how a document is split:
- Hierarchy: Construct a heading tree and produce self-contained chunks, each carrying its full ancestral path (e.g. Part 1 Chapter 3 Section 2 + body text). Best for highly structured texts — such as legal statutes, regulations, contracts, and technical specs — where each chunk must be identifiable by its position in the hierarchy.
- Group: Split the document flat at a chosen heading level, merging adjacent small sections to ensure semantic flow. Chunks exclude ancestral path. Best for documents with flowing, contextually connected content — such as books, manuals, reports, and articles — where narrative coherence depends on keeping adjacent paragraphs together.
#### Separate parent-heading content
:::tip NOTE
Available only when **Hierarchy** is selected.
:::
When enabled, chunks include only their heading path and content; content immediately following a parent heading is kept as a separate chunk.
#### Set first chunk as global context
:::tip NOTE
Available only when **Hierarchy** is selected.
:::
Treats the first split as a global heading to maintain consistent context across the document hierarchy. Ideal for resumes where the first section identifies the subject.
#### H3
Specifies the heading level to define chunk boundaries:
@@ -31,8 +54,9 @@ Specifies the heading level to define chunk boundaries:
- H2
- H3 (Default)
- H4
- H5
Click **+ Add** to add heading levels here or update the corresponding **Regular Expressions** fields for custom heading patterns.
Click **+ Add regular expressions** to add heading levels here or update the corresponding **Regular Expressions** fields for custom heading patterns.
### Output