Blog - K2view

Gartner RAG Tips for Grounding LLMs with Relevant Internal Data

Written by Ian Tick | January 28, 2024

Learn how to prepare for RAG with this FREE condensed version of the 2024 Gartner report, “How to Supplement Large Language Models with Internal Data”. 

From RAG to Riches

Enterprises that can leverage Large Language Models (LLMs) effectively are likely to be more operationally efficient and commercially competitive.

Retrieval-Augmented Generation (RAG) is a design pattern that augments an LLM with fresh, trusted data retrieved from authoritative internal knowledge bases and enterprise systems, to generate more informed and reliable responses.

According to a 2024 Gartner report entitled, “How to Supplement Large Language Models with Internal Data”, enterprises can prepare themselves for RAG implementations by taking several considerations into account, listed as Gartner RAG tips in this article.

Learn more in the complete guide to retrieval-augmented generation

Gartner RAG Tip 1: Focus Your Scope

 Large Language Models empower RAG to: 

  • Write copy

  • Use different tones of voice 

  • Translate text into instructions, queries, or different languages 

RAG enables enterprises to access (typically Internal) data outside the foundation model (LLM) and adjusts the prompts for relevancy. Designed to deliver business value, RAG can: 

  • Integrate updated or real-time information

  • Identify the knowledge source

  • Rank the responses for relevancy

  • Enhance output accuracy and coherence 

Inspired by Gartner, this diagram illustrates the retrieval-augmented generation framework: 

  1. The user (at the top) prompts the retrieval model.
  2. The retrieval model queries the company's internal sources (knowledge  bases and enterprise systems) for the most relevant docs and dataset.
  3. The retrieval model augments the user's original prompt with additional contextual information and passes it on as input to the generation model (LLM API).
  4. The LLM uses the augmented prompt to generate a more informed response and then sends it back to the user. 

Gartner RAG Tip 2: Select Your Use Case 

RAG use cases can span multiple enterprise domains, as shown in the following table: 

Department 

Objective 

Types of RAG data 

Customer service 

Personalize the chatbot experience to each customer to respond more effectively. 

  • Customer feedback and/or rating 

  • Contract status 

  • Next or related questions 

  • Workflow for call routing 

  • Current phone prompts 

  • Performance metrics (e.g., first-call resolution, customer satisfaction) 

Sales and marketing 

Engage with potential customers on a website or via chatbot to describe products and offer recommendations. 

  • Market data 

  • Economic information 

  • Stock market indexes 

  • Mergers and acquisitions 

  • Product documentation 

  • Customer profiles and demographics 

  • Targeted personas and behaviors 

Legal and compliance 

Draft and summarize legal documents and create compliance policies and training materials. 

  • Case law and precedents 

  • Judgements 

  • Government regulations 

  • Social media relationships 

  • Criminal record databases 

  • Newsfeeds 

HR

Generate interview questions, job descriptions, employment agreements, survey results, and suggestions for company activities and events. 

  • Company policies (vacation, remote work, expense reimbursement) 

  • Benefits 

  • Employee demographics 

  • Periodic evaluations 

Gartner RAG Tip 3: Classify Your Data 

Data is generally classified as structured, semi-structured, or unstructured. The distinction is critical to your RAG initiative because it helps you determine the database technologies, security features, storage needs, query methods, processing, and architectural considerations best suited to your needs.

Start by identifying and classifying your underlying data, as shown in this sample data taxonomy diagram. 

Some of your most valuable insights might be hidden in unstructured textual data, typically in the form of PDFs and other file types.  

For your first RAG pilot, make sure your:  Note that unstructured data: 
  • Use case involves your internal data
  • Has no set format 
  • Internal data is in a text format
  • Can’t be defined in a schema

Gartner RAG Tip 4: Make Your Data RAG-Friendly 

As discussed in the previous section, RAG enables unstructured data to be identified, interpreted, and applied with the right context. But you’ll need to parse, extract, or chunk the data, convert it to embeddings, and then safely store those embeddings for retrieval when prompted.

To be RAG-friendly, make sure your unstructured data files can: 

  • Support text extraction

  • Be stored in a normal or vector search engine 

Then answer the following questions about your… 

Data  Data sources 
Do you know who produced the data and where it’s from?  What’s in these documents? 
Is the data producer trustworthy?  When were they created? 
Can you contact the data producer for support?  How much data can be extracted from these documents? 
Is there metadata about the data?  How easily can this data be organized for your RAG use case? 
If so, is it reliable, consistent, complete, and up to date?  Are there other data sources you could use? 

Gartner RAG Tip 5: Choose Your Technology 

Knowledge graphs and vector databases are both technologies that enable RAG and can be used alone or together.

Knowledge graphs

Knowledge graphs interpret and understand existing information, relationships in a domain, and rules that connect one entity to another semantically. Knowledge graphs can extract metadata embedded in image files, documents, and PDFs. This capability allows for search and query of file formats, creation/modification dates, authors, keywords, and titles.

Vector databases

Vector databases enable enterprises to retrieve data based on its meaning or context, and then to use that data to augment the generative AI prompts. Built to process unstructured data at scale, they improve the quality and relevance of the resulting generated outputs. 

Retrieval-Augmented Generation via Data Products 

Data products – reusable data assets that combine data with everything needed to make them independently accessible by authorized users – power RAG use cases via insights derived from an organization’s internal data and information.  

Data products retrieve fresh, trusted internal data into the RAG framework in real time, to: 

  • Integrate the customer 360 / product 360 data from all relevant data sources 

  • Translate data and context into relevant prompts 

  • Feed it to the LLM along with the user’s query 

The LLM then generates an accurate and personalized response for the user (via a RAG chatbot, for example).  

Data products can be accessed via API, CDC, messaging, streaming – in any combination – to unify data from multiple source systems.

Combining RAG with real-time data products is useful for many use cases, such as: 

Accelerating issue resolution Creating hyper-personalized marketing campaigns Generating personalized cross-/up-sell recommendations for call center agents Detecting fraud
by identifying suspicious activity before damage can be done

Learn more about the Data Product Platform that powers RAG.