Skip to content

Hallucination end point to fetches embeddings causing duplication of efforts #66

Description

@InfosysResponsibleAI

Module Name.
responsible-ai-Hallucination

**Feature request **
Hallucination score calculation i.e gEval end point fetching relevant documents from vector store and then calculating the hallucination score.

@InfosysResponsibleAI
Solution expectation
When use cases are having logic of getting documents from vector DB and again this gEval end point spending extra run time fetching relevant document which is issue from both run time as well and costing point of views.
We are looking at decoupling the logic of vector DB retrieval and calculation of score into 2 separate end points.

Alternatives
Also support for alternative models giving the vector DB and use that any of end point in hallucination score calculation

Metadata

Metadata

Labels

suggestSuggest a new feature

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions