Yeah, we were playing around with doing some semantic chunking. Works okay for some use cases. We have some ideas to go further on that.
Generally we have found that recursive chunking and character chunking tend to be short sighted.
Generally we have found that recursive chunking and character chunking tend to be short sighted.
Why not capture a few strategies that the LLM returns as code that can be properly audited (and ran locally improving the overall performance)?
The idea of auditing the strategy is interesting. The flow that we have used for the semantic chunkers up to date has been along these lines where we : 1) Use the utility to generate the code snippets (and do some manual inspection) 2) Test the code snippets against some sample text 3) Validate the results