1,336 karma · joined March 30, 2011
If there is one problem I have to pick to to trace in LLMs, I would pick hallucination. More tracing of "how much" or "why" model hallucinated can lead to correct this problem. Given the explanation in this post about hallucination, I think degree of hallucination can be given as part of response to the user?
I am facing this in RAG use case quite - How do I know model is giving right answer or Hallucinating from my RAG sources?
In my use case, it's going to be exposed to various kind of stakeholders and there will be versatility of user queries. I can't pre-create views/aggregations for all scenarios.
My schema is - 90+ Tables, 2500+ Columns, well documented
From your experience, does Cube look a fit? My use cases will definitely have JOINS.
Something on similar lines which many may link, Research Rabbit - https://www.researchrabbit.ai/
Someone open sourced it with langchain
1. Does it take care of Bot detection. Most sites will have it.
2. Is this something similar to Firecrawl - https://www.firecrawl.dev/
I did not like finance much, but building a fintech system really teaches a lot, not only from technology perspective but from managing stakeholders, processes, compliance, dealing with all kinds of finance-specific issues.
One should always work in fintech, at some point of time in career.
Getting better models at the edge would help in this to some extent as it will decentralise the runtime of AI (still model training would happen in data centers)