Replies: 1 comment
-
🤖 Hey there, @nshern! Nice to see you back with more questions. Hope you've been doing well! In the context of RAG on documents structured as verbatim statements from people, it would be a good practice to consider each statement as a single node with metadata. This approach is supported by the The
The In terms of what constitutes a "good node", it would typically be a node that accurately represents a single statement from a person, includes relevant metadata (such as surrounding sentences for context), and is easily processed by the rest of your application. However, the exact definition of a "good node" may vary depending on your specific use case and requirements. You can find more information about the Sources
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello! I have a general question I hope someone can help me with:
Say I want to do RAG on documents that are meeting notes that are structured so that it is a bunch of verbatim statements from people, structured like
person 1: bla bla bla, 11:46
person2: bla bla bla , 11:47
person1: blablablablabla, 11:50
...
person3: blabla, 14:45
i.e. a structure that is person, statement, timestamp
Is it a good idea to define each node so that it is a single statement, together with metadata being name of person and time and with no chunk overlap? Or should I just let the node parser do it automatically?
Where can I find some information regarding this and what makes up a "good node"?
Beta Was this translation helpful? Give feedback.
All reactions