4 ms·
Very cool! The training objective is clever. The 50+ filters at Ecodash.ai for 90,000 plants came from a custom RAG model on top of 800,000 raw web pages. Bec
by legel 1y ago
Very cool!
The training objective is clever.
The 50+ filters at Ecodash.ai for 90,000 plants came from a custom RAG model on top of 800,000 raw web pages. Because LLM’s are expensive, chunking and semantic search for figuring out what to feed into the LLM for inference is a key part of the pipeline nobody talks about. I think what I did was: run all text through the cheapest OpenAI embeddings API… then, I recall that nearest neighbor vector search wasn’t enough to catch all relevant information, for a given query to be answered by an LLM. So, I remember generating a large number of diverse queries, which mean the same thing (e.g. “plant prefers full sun”, “plant thrives in direct sunlight”, “… requires at least 6 hours of light per day”, …) and then doing nearest neighbor vector search on all queries, and using the statistics to choose what to semantically feed into RAG.
- throwaway7783 1y agoHave you tried the bm25 + vector search + reranking pipeline for this?
- searchguy 1y agoHey, thanks for unpacking what you did at ecodash.ai. Did you manually curate the queries that you did LLM query expansion on (generating a large number of diverse queries), or did you simply use the query log?