mchorfa/auto-evaluator

Auto-evaluator 🧠 📝

Context

Document Question-Answering is a popular LLM use-case. LangChain makes it easy to assemble LLM components (e.g., models and retrievers) into chains that support question-answering: input documents are split into chunks and stored in a retriever, relevant chunks are retrieved given a user question and passed to an LLM for synthesis into an answer.

Challenge

The quality of QA systems can vary considerably; for example, we have seen cases of hallucination and poor answer quality due specific parameter settings. But, it is not always obvious to (1) evaluate the answer quality in a systematic way and (2) use this evaluation to guide improved QA chain settings (e.g., chunk size) or components (e.g., model or retriever choice).

App overview

This app aims to address the above limitations. Recent work from Anthropic has used model-written evaluation sets. OpenAI and others have shown that model-graded evaluation is an effective way to evaluate models. This app combines both of these ideas into a single workspace, auto-generating a QA test set and auto-grading the result of the specified QA chain.

Usage

The app can be used in two ways:

• Demo: We pre-loaded a document (a transcript of the Lex Fridman podcast with Andrej Karpathy) and a set of 5 question-answer pairs from the podcast. You can configure QA chain(s) and run an experiment.

• Playground: Input a set of documents that you want to ask questions about. Optionally, also include your own test set of question-answer pairs related to the documents; see an example here. If you do not supply a test set, the app will auto-generate one. If the test set is smaller than the desired number of eval questions specified in the top left, the app will auto-generate the remainder.

Building the document retrieval:

• The app will build a retriever for the input documents.
• Retriever is a Langchain abstraction that accepts a question and returns a set of relevant documents.
• The retriever can be selected by the user in the drop-down list in the configurations (red panel above).

Test set generation:

• The app will auto-generate a test set of question-answer pair on the doc(s).
• To do this, it uses the Langchain QAGenerationChain with the default prompt here.

LLM question-answering:

• For each question, we use a RetrievalQA chain to answer it.
• This will fetch chunks that are relevant to the question from the retriever and pass them to the LLM.
• We expose the QA_CHAIN_PROMPT used for to pass this context to the LLM here.

Model-graded evaluation:

• We let the user select from a number of model-graded evaluation prompts:

(1) The app will evaluate the relevance of the retrieved documents relative to the question.

(2) The app will evaluate the similarity of the LLM generated answer relative to ground truth answer.

• The prompts for both can be seen here
• Users can select which grading prompt to use. Here are some notes in prompt selection from our experience.

Experimental results:

• The app will produce a table summarizing the results.
• It shows the question and the ground truth (expected) answer.
• It shows the chain-generated answer.
• It shows the binary score (PASS / FAIL) for retrieval and the answer.
• It shows the latency for retrieval and LLM answer summarization per question.
• It shows the model grader output (the raw output of the grading prompt).

User inputs

The left panel of the app (shown in red in the above image) has several user-configurable parameters.

Number of eval questions - This is the number of question-answer pairs to auto-generate for the given inputs documents. As mentioned above, question-answer pair auto-generation will use Langchain's QAGenerationChain with prompt specified here.

Chunk size - Number of characters per chunk when the input documents are split. This can impact answer quality. Retrievers often use text embedding similarity to select chunks related to the question. If the chunks are too large, each chunk may contain more information unrelated to the question, which may degrade the summarized answer quality. If chunks are too small, important context may be left out of the retrieved chunks.

Overlap - The overlap in characters between chunks.

Embedding - The method used to embed chunks.

Retriever - The method used to retrieve chunks that are relevant to the user question. The default vector database used for similarity search is FAISS, but support for others is a welcome addition. You can also try other methods, such as SVM or TF-IDF.

Number of chunks to retrieve - Number of chunks retrieved. More chunks can improve performance by giving the LLM more context for answer summarization.

Model - LLM for summarization of retrieved chunks into the answer.

Grading prompt style - The prompt choice for model-graded evaluation. As mentioned above, the prompts can be seen here. More prompts would be a welcome addition. For example, with the Descriptive prompt, you will see a more detailed output with model grade justification.

Logging experiments

A user can select the desired configuration and then choose Re-Run Experiment.

This will run the new chain on the existing test set.

The results from all experiments will be summarized in the table and chart.

Contributing

Run the backend from api folder:

 pip install -r requirements.txt
 uvicorn evaluator_app:app

Test the api locally:

curl -X POST -F "files=@docs/karpathy-lex-pod/karpathy-pod.txt" -F "num_eval_questions=1" -F "chunk_chars=1000" -F "overlap=100" -F "split_method=RecursiveTextSplitter" -F "retriever_type=similarity-search" -F "embeddings=OpenAI" -F "model_version=gpt-3.5-turbo" -F "grade_prompt=Fast" -F "num_neighbors=3" http://localhost:8000/evaluator-stream

Run the frontend from nextjs folder and view web app at specified URL (e.g., http://localhost:3000/):

yarn install
yarn dev

Environment Variables

Front-end:

.env.local contains the env variables needed to run the project.

Back-end:

Specify the API keys for any models that you want to use.

OPENAI_API_KEY=
ANTHROPIC_API_KEY=

Deployment

The front-end is deployed to Vercel.

The back-end is deployed to Railway.