zlacker

[parent] [thread] 4 comments
1. johnjw+(OP)[view] [source] 2024-05-30 16:12:06
Author here: you're for sure right -- it's not a problem with RAG the theoretical concept. In fact, I think RAG implementations should likely be specific to their use cases (e.g. our hybrid search approach works well for customer support, but I'm not sure if it would work as well in other contexts, say for legal bots).

I've seen the whole gamut of RAG implementations as well, and the implementation, specifically prompting and the document search has a lot to do with the end quality.

replies(1): >>verdve+Ee
2. verdve+Ee[view] [source] 2024-05-30 17:21:38
>>johnjw+(OP)
re: legal, I saw a post on this idea where their RAG system was designed to return the actual text from the document rather than a LLM response or summary. The LLM played a role in turning the query into the search params, but the insight was that for certain kinds of documents, you want the actual source because of the existing, human written summary or the detailed nuances therein
replies(1): >>gradys+zZ
◧◩
3. gradys+zZ[view] [source] [discussion] 2024-05-30 21:59:35
>>verdve+Ee
Sounds more like Generation Augmented Retrieval in that case.
replies(2): >>verdve+1M1 >>rjvs+VZ1
◧◩◪
4. verdve+1M1[view] [source] [discussion] 2024-05-31 06:57:33
>>gradys+zZ
It wasn't this GAR post, I remember them calling out legal docs explicitly, might have seen it on Twitter

https://blog.luk.sh/rag-vs-gar

◧◩◪
5. rjvs+VZ1[view] [source] [discussion] 2024-05-31 09:41:35
>>gradys+zZ
Do you happen to have any good references for GAR implementation?
[go to top]