microsoft / microsoft/rag-experiment-accelerator

Can we separate the generation of Q&A from the experiment process?

Open
#236 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
311
Forks
111
PR merge metrics
No merged PRs in 30d

Description

As part of an engagement, we are experimenting with the rag accelerator and find it extremely useful!

For evaluation, our plan is to leverage two sources of information:

  1. Manually curated questions and answers that the SMEs created for us (around 15 pairs)
  2. Generate additional questions and answers using LLMs

If I understand correctly, in 02_qa_generation, we generate these pairs and use those for evaluations. This process also generates the actual response from the LLM given the system prompt, user prompt and retrieved context.

My question is, how would you suggest to separate the two? If we generate q&a pairs every time, we might get different evaluation datasets and the experiments would not be comparable. In addition, we want to generate a q&a dataset and review it with our SMEs.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the 02_qa_generation process to understand where question-answer generation and LLM responses are combined. Define the separation so a generated dataset can be saved, reviewed by SMEs, and reused for comparable experiments without regenerating it each time.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ai, machine-learning, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.