Re-ranking retrieved results in Prompt Engineering / GenAI - Model Pipeline Trace

Model Pipeline - Re-ranking retrieved results

This pipeline improves search results by first retrieving many items, then re-ordering them to show the best matches on top.

Data Flow - 5 Stages

1Initial Retrieval

1 query x large document database→Retrieve top 100 documents using basic search→100 documents

Query: 'best Italian restaurants' → Retrieved 100 restaurant descriptions

↓

2Feature Extraction

100 documents→Convert documents and query into vector features→100 vectors x 512 features

Each restaurant description converted to a 512-length vector

↓

3Re-ranking Model

100 vectors x 512 features→Score each document's relevance to query using a neural network→100 scores

Scores like 0.85, 0.78, 0.95 indicating relevance

↓

4Sort by Score

100 documents + 100 scores→Sort documents descending by score→100 documents ordered

Top document has score 0.95, second 0.90, etc.

↓

5Final Output

100 ordered documents→Return top 10 documents to user→10 documents

Top 10 restaurant descriptions shown to user

Training Trace - Epoch by Epoch

Loss
0.7 | *
0.6 | **
0.5 | ***
0.4 | ****
0.3 | *****
0.2 | ******
     ----------------
      1 2 3 4 5 Epochs

Epoch	Loss ↓	Accuracy ↑	Observation
1	0.65	0.60	Model starts learning to rank documents better
2	0.48	0.72	Loss decreases, accuracy improves as model learns
3	0.35	0.81	Model shows good ranking ability
4	0.28	0.86	Further improvement, loss steadily decreases
5	0.22	0.90	Model converges with high accuracy

Prediction Trace - 4 Layers

Layer 1: Input Query and Retrieved Documents

Layer 2: Neural Network Scoring

Layer 3: Sorting

Layer 4: Select Top Results

Model Quiz - 3 Questions

Why do we convert documents into vectors before re-ranking?

A Because vectors remove all meaning from documents

B Because vectors make documents shorter

C Because vectors let the model compare documents numerically

D Because vectors are easier to read by humans

Key Insight

Re-ranking improves search by using a model to score and reorder results, making the best matches appear first. This step refines initial broad retrieval to a focused, relevant list.

Practice

1.

What is the main purpose of re-ranking retrieved results in a search system?

easy

A. To sort the initial search results again using a better scoring method

B. To remove duplicate results from the search output

C. To speed up the initial search query processing

D. To translate results into different languages

Solution

1. Step 1: Understand the role of re-ranking

   Re-ranking means sorting results again after the first search to improve order.

2. Step 2: Identify the goal of re-ranking

   The goal is to use a smarter scoring method to show the most relevant results at the top.

3. Final Answer:

   To sort the initial search results again using a better scoring method -> Option A

4. Quick Check:

   Re-ranking = better sorting [OK]

Hint: Re-ranking means sorting results again for better relevance [OK]

Common Mistakes:

• Confusing re-ranking with removing duplicates
• Thinking re-ranking speeds up initial search
• Assuming re-ranking translates results

2.

Which of the following code snippets correctly represents a simple re-ranking step that sorts a list of results by their score in descending order?

results = [{'id': 1, 'score': 0.5}, {'id': 2, 'score': 0.9}, {'id': 3, 'score': 0.7}]
# Re-rank results here

easy

A. results.sort(reverse=True)

B. results.sort(key=lambda x: x['id'])

C. results.sort(key=lambda x: x['score'])

D. results.sort(key=lambda x: x['score'], reverse=True)

Solution

1. Step 1: Identify sorting by score descending

   We want to sort by 'score' in descending order, so reverse=True is needed.

2. Step 2: Check each option

   results.sort(key=lambda x: x['score'], reverse=True) sorts by 'score' with reverse=True, which is correct. Others either sort by 'id' or ascending score or missing key.

3. Final Answer:

   results.sort(key=lambda x: x['score'], reverse=True) -> Option D

4. Quick Check:

   Sort by score descending = results.sort(key=lambda x: x['score'], reverse=True) [OK]

Hint: Sort with key and reverse=True for descending order [OK]

Common Mistakes:

• Forgetting reverse=True for descending sort
• Sorting by wrong key like 'id'
• Using sort without key causing error

3.

Given the following code that re-ranks search results by a new score, what will be the output after re-ranking?

results = [
  {'id': 'a', 'score': 0.3},
  {'id': 'b', 'score': 0.8},
  {'id': 'c', 'score': 0.5}
]

# New scores from a re-ranker
new_scores = {'a': 0.9, 'b': 0.4, 'c': 0.7}

for r in results:
    r['score'] = new_scores[r['id']]

results.sort(key=lambda x: x['score'], reverse=True)
print([r['id'] for r in results])

medium

A. ['b', 'c', 'a']

B. ['a', 'c', 'b']

C. ['c', 'a', 'b']

D. ['a', 'b', 'c']

Solution

1. Step 1: Update scores with new_scores

   Results get scores: 'a' = 0.9, 'b' = 0.4, 'c' = 0.7.

2. Step 2: Sort results by updated score descending

   Sorted order by score: 0.9 ('a'), 0.7 ('c'), 0.4 ('b').

3. Final Answer:

   ['a', 'c', 'b'] -> Option B

4. Quick Check:

   Sort by new scores descending = ['a', 'c', 'b'] [OK]

Hint: Replace scores then sort descending by score [OK]

Common Mistakes:

• Sorting by old scores instead of new
• Sorting ascending instead of descending
• Mixing up ids and scores

4.

Identify the error in this re-ranking code snippet and select the fix:

results = [{'id': 1, 'score': 0.2}, {'id': 2, 'score': 0.5}]
new_scores = {1: 0.7, 2: 0.9}

for r in results:
    r['score'] = new_scores[r['id']]

results.sort(key=lambda x: x['score'], reverse=True)
print(results)

medium

A. Use sorted() instead of sort() to avoid in-place sorting

B. Change new_scores keys to strings to match 'id' type

C. No error; code runs correctly and sorts results

D. Add a try-except block to handle missing keys

Solution

1. Step 1: Check key types in new_scores and results

   Both use integer keys for 'id', so lookup works correctly.

2. Step 2: Verify sorting and printing

   Sorting by updated 'score' descending is valid and prints sorted list.

3. Final Answer:

   No error; code runs correctly and sorts results -> Option C

4. Quick Check:

   Matching key types = no error [OK]

Hint: Check key types match for dictionary lookups [OK]

Common Mistakes:

• Assuming string keys when they are integers
• Thinking sort() causes error without reason
• Adding unnecessary try-except blocks

5.

You have a list of 5 retrieved documents with initial scores. You want to re-rank them using a machine learning model that outputs a relevance score. Which approach best improves the final ranking?

1. Use the model scores to replace initial scores and sort descending.
2. Combine initial and model scores by averaging, then sort descending.
3. Sort only by initial scores, ignoring model scores.
4. Randomly shuffle results to avoid bias.

hard

A. Combine initial and model scores by averaging, then sort descending

B. Use the model scores to replace initial scores and sort descending

C. Sort only by initial scores, ignoring model scores

D. Randomly shuffle results to avoid bias

Solution

1. Step 1: Understand re-ranking with model scores

   Replacing scores fully may ignore useful initial info; combining scores balances both.

2. Step 2: Evaluate options for best ranking

   Averaging initial and model scores uses all info, improving relevance and stability.

3. Final Answer:

   Combine initial and model scores by averaging, then sort descending -> Option A

4. Quick Check:

   Combine scores for best re-ranking [OK]

Hint: Blend initial and model scores for better ranking [OK]

Common Mistakes:

• Replacing scores blindly losing initial info
• Ignoring model scores completely
• Random shuffling breaks relevance