You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/tutorial-rag-build-solution-maximize-relevance.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: 'RAG Tutorial: Relevance tuning'
2
+
title: 'RAG tutorial: Tune relevance'
3
3
titleSuffix: Azure AI Search
4
4
description: Learn how to use the relevance tuning capabilities to return high quality results for generative search.
5
5
@@ -16,15 +16,15 @@ ms.date: 10/05/2024
16
16
17
17
In this tutorial, learn how to improve the relevance of search results used in RAG solutions. Relevance tuning can be an important factor in delivering a RAG solution that meets user expectations. In Azure AI Search, relevance tuning includes L2 semantic ranking and scoring profiles.
18
18
19
-
To implement some of these techniques, you revisit the index schema to add configurations for semantic ranking and scoring profiles. Other relevance tuning techniques can be applied to the queries themselves.
19
+
To implement these capabilities, you revisit the index schema to add configurations for semantic ranking and scoring profiles. You then rerun the queries using the new constructs.
20
20
21
21
In this tutorial, you modify the existing search index and queries to use:
22
22
23
23
> [!div class="checklist"]
24
24
> - L2 semantic ranking
25
25
> - Scoring profile for document boosting
26
26
27
-
This tutorial updates the search index created by the [indexing pipeline](tutorial-rag-build-solution-pipeline.md). Updates don't affect the existing content, so no rebuild is necessary and you don't need to rerun the indexer.
27
+
This tutorial updates the search index created by the [indexing pipeline](tutorial-rag-build-solution-pipeline.md). Updates don't affect the existing content, so no rebuild is necessary and you don't need to rerun the indexer.
28
28
29
29
> [!NOTE]
30
30
> There are more relevance features in preview, including vector query weighting and setting minimum thresholds, but we omit them from this tutorial becaues they aren't yet available in the Azure SDK for Python.
@@ -122,7 +122,7 @@ In a previous tutorial, you [designed an index schema](tutorial-rag-build-soluti
122
122
123
123
## Update queries for semantic ranking and scoring profiles
124
124
125
-
In a previous tutorial, you [ran queries](tutorial-rag-build-solution-query.md) that execute on the search engine, andpass the response and other information to an LLMfor chat completion.
125
+
In a previous tutorial, you [ran queries](tutorial-rag-build-solution-query.md) that execute on the search engine, passing the response and other information to an LLMfor chat completion.
126
126
127
127
This example modifies the query request to include the semantic configuration and scoring profile.
Copy file name to clipboardExpand all lines: articles/search/tutorial-rag-build-solution-query.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: 'RAG Tutorial: Search using an LLM'
2
+
title: 'RAG tutorial: Search using an LLM'
3
3
titleSuffix: Azure AI Search
4
4
description: Learn how to build queries and engineer prompts for LLM-enabled search on Azure AI Search. Queries used in generative search provide the inputs to an LLM chat engine.
5
5
@@ -132,7 +132,7 @@ It's expected for LLMs to return different answers, even if the prompt and queri
132
132
133
133
## Add a filter
134
134
135
-
Recall that you created a `locations` field using applied AI, populated with places recognized by the Entity Recognition skill. The field definition for locations includes the `filterable` attribute. Let's repeat the previous request, but this time adding a filter that selects on the term *ice* in the locations field. A filter introduces inclusion or exclusion criteria. The search engine is still doing a vector search on `"how much of earth is covered by water"`, but it's now excluding matches that don't include *ice*. For more information about filtering on string collections and on vector queries, see [text filter fundamentals](search-filters.md#text-filter-fundamentals),[Understand collection filters](search-query-understand-collection-filters.md), and [Add filters to a vector query](vector-search-filters.md).
135
+
Recall that you created a `locations` field using applied AI, populated with places recognized by the Entity Recognition skill. The field definition for locations includes the `filterable` attribute. Let's repeat the previous request, but this time adding a filter that selects on the term *ice* in the locations field. A filter introduces inclusion or exclusion criteria. The search engine is still doing a vector search on `"how much of earth is covered by water"`, but it's now excluding matches that don't include *ice*. For more information about filtering on string collections and on vector queries, see [text filter fundamentals](search-filters.md#text-filter-fundamentals),[Understand collection filters](search-query-understand-collection-filters.md), and [Add filters to a vector query](vector-search-filters.md).
136
136
137
137
Replace the search_results definition with the following example that includes a filter:
0 commit comments