Disclaimer: I am curating LLM-tools on github [1] A few thoughts: * allow for custom endpoint URLs, this way people can use open source LLMs with a fake openAI API backend like basaran[2] or llama-api-server[3] * look into better embedding methods for info-retrieval like InstructorEmbeddings or Document Summary Index * Don't use a single embedding per content item, use multiple to increase retrieval quality 1 https:/…
* Don't use a single embedding per content item, use multiple to increase retrieval quality Can you share some specific examples of what you mean by this? How would you process specific info types (eg: news article, or web page, or product catalogue data) this way, and how would you handle retrieval that makes the quality "better"? *Edit: Thanks for all replies so far - yes I am aware about splitting or chunking the…
The other often neglected approach is to use an LLM to derive new content and use the embedding of this as well.
E.g. ask the LLM “give me a list of questions that can be answered by the following passage”
You then use embeddings of the generated questions instead of embeddings of the original content.