Aug 14, 2023
How to Build an End-to-End RAG Pipeline with Unstructured’s API
Let’s say you have a lot of PDFs in your Google Cloud Storage (GCS) and you want to leverage a vector database to give your large language model (LLM) more context for more accurate and up to date answers, you first need to extract, clean, and transform those PDFs into a format that an LLM can understand (e.g. JSON). Unstructured’s library can help.
Unstructured.io offers a powerful toolkit that handles the ingestion and data preprocessing step, allowing you to focus on the more exciting downstream steps in your machine learning pipeline. Unstructured has over a dozen data connectors that easily integrate with various data sources, including AWS S3, Discord, Slack, Wikipedia, and more.
In this guide we will go through a step-by-step guide on how to grab your data from GCS, and preprocess that data and upload it to a vector database for Retrieval Augmented Generation (RAG).
Install Unstructured Google Cloud connectors here
Obtain Unstructured API Key here
Obtain OpenAI API Key here
Obtain Pinecone API key here
A Google Cloud Storage (GCS) bucket full of documents you want to process
Basic knowledge of command line operations
Enable GCS Access:
In order to access your files from GCS you need to grant access to reading the buckets within your GCS account. If you are unfamiliar with this process I will go over a basic example but if you are already familiar with the steps feel free to skip to the next section.
Navigate to your Google Cloud Console (link)
Click on the project that you plan on grabbing data from
On the left side of the screen click IAM & Admin -> Service Accounts
Click “+ Create Service Account” and fill in the fields
Once you’ve created the new service account click on it and go to “KEYS”
Click “ADD KEY”->”Create new key”->JSON
That will download a JSON file with your keys. Please ensure that these keys are properly stored as they pose a security risk.
Place the JSON file somewhere safe and in a path you can access later on
Run Unstructured API with GCS Connector:
With your Unstructured API key and GCS bucket ready, it’s time to run the Unstructured API. To run the `unstructured-ingest` command, you need to install the unstructured open-source library that can be easily obtained from this GitHub repository.
Follow the instructions in the repository to install the library and please make sure to install the additional dependencies below:
!pip install "unstructured[gcs,all-docs]" langchain openai pinecone-client
Once you installed the additional dependencies, you are good to run the API. For this tutorial, I’ve elected to run the API in a python notebook.
# Add the environment variable for the GCP service account credentials
os.environ['GOOGLE_APPLICATION_CREDENTIALS'] = '/Path/to/your/keyfile.json'
command = [
os.environ[‘GOOGLE_APPLICATION_CREDENTIALS’] =/path/to/your/keyfile.json — Add the environment variable for the GCP service account credentials
“gcs” — specifies the data connector
Set the output directory using ` — structured-output-dir` parameter
Specify ` — num-processes` to distribute the workload across multiple processes
Include ` — api-key` from the earlier step in your API call
Use the ` — partition-by-api` flag to indicate running the partition through API rather than the library
We are proud to introduce our free-to-use API, tailor-made for enthusiasts and developers keen on prototyping. We’ve allocated a specific number of dedicated workers to ensure seamless operation and to cater to our user community. However, we understand the needs of larger corporations and heavy-duty tasks. With this in mind, we are excited to announce that an enterprise-grade API is on the horizon.
Review the API output:
Once the command completes, you’ll find the structured outputs in your specified output directory. These files contain the extracted information from your unstructured data, ready for analysis or further processing.
When we build RAG systems, our LLMs model only performs as well as the context that is provided to them. For that reason, we want to remove unnecessary textual elements found in our files. Fortunately Unstructured classifies text by element types and when Unstructured finds elements that it can’t classify it labels them as “UncategorizedText”. Often that “UncategorizedText” is unhelpful and distracting to our LLM. In this tutorial we will remove those “UncategorizedText” elements with the following helper function.
def remove_element_from_json(filepath, item_to_remove):
# Read the file and load its contents as JSON
with open(filepath, 'r') as file:
data = json.load(file)
# Filter out the elements with the specified 'type'
updated_data = [item for item in data if item['type'] != item_to_remove] # Write the updated data back to the file
with open(filepath, 'w') as file:
json.dump(updated_data, file, indent=4)
Now you can call the above helper function by specifying the file path to the document and the element type you’d like to remove.
filepath = '/YOUR/OUTPUT/PATH'
Load Json Files Into Langchain:
The next step is to load in your cleaned and processed structured data into LangChain’s document loaders. In this case we will use the UnstructuredFileLoader by LangChain.
from langchain.document_loaders import UnstructuredFileLoader
# Now you will load to files outputted from the Unstructured API. You'll find the files in the output directory.
loader = UnstructuredFileLoader(
docs = loader.load()
Chunk the Text Files:
Next we will need to chunk the original documents so that our Large Language Models (LLMs) can process the potentially long documents. A current limitation of LLMs is that they can only process a certain amount of context. We chunk data to make the pieces of text digestible for them.
For the purpose of this tutorial I have chosen to go with LangChain’s RecursiveCharacterTextSplitter however they have a variety of different chunking methods found here.
text_splitter = RecursiveCharacterTextSplitter(
docs = text_splitter.split_documents(docs)
Setting up Pinecone:
Once we’ve chunked our data now we can embed it and store it in a vector database. In this demo I am going to use Pinecone however there are a variety of different options each with their own strengths.
# Storing API keys like this poses a security risk. Only do this in prototyping
os.environ['PINECONE_API_KEY'] = "<PINECONE-API-KEY>"
# Pinecone Environment Variable
os.environ['PINECONE_ENV'] = "<PINECONE-LOCATION>"pinecone.init(
api_key=os.getenv("PINECONE_API_KEY"), # find at app.pinecone.io
environment=os.getenv("PINECONE_ENV"), # next to api key in console
)index_name = "gcs-demo"
# First, check if our index already exists. If it doesn't, we create it
if index_name not in pinecone.list_indexes():
# we create a new index
Create Helper Functions:
The next step is once we’ve initialized our Pinecone database we need to create a helper function to grab all the relevant chunks of information from our vector database to be later used by our LLM ( inspiration).
limit = 3600
embed_model = "text-embedding-ada-002"
res = openai.Embedding.create(
) # retrieve from Pinecone
xq = res['data']['embedding'] # get relevant contexts
res = index.query(xq, top_k=3, include_metadata=True)
contexts = [
x['metadata']['text'] for x in res['matches']
] # build our prompt with the retrieved contexts included
prompt_start = (
"Given the contextual information and not prior knowledge, answer the question. If the answer is not in the context, inform the user that you can't answer the question.\n\n"+
prompt_end = (
# append contexts until hitting limit
for i in range(1, len(contexts)):
if len("\n\n---\n\n".join(contexts[:i])) >= limit:
prompt = (
elif i == len(contexts)-1:
prompt = (
Now that we have a helper function to retrieve the relevant chunks of information we need a helper function to take in our augmented prompt and feed it into our LLM.
# query text-davinci-003
res = openai.Completion.create(
Query Vector Database:
With our two helper functions, we can now leverage our vector database to retrieve relevant pieces of information to help our LLM answer domain specific questions.
query = "A question you'd like to ask about your PDF"
# first we retrieve relevant items from Pinecone
query_with_contexts = retrieve(query)
Once we’ve retrieved the necessary context we can feed it into our LLM to answer our question.
# then we complete the context-infused query
In this blog we’ve gone from unstructured raw PDFs stored in a GCS bucket to pre-processing them, and uploading them to a vector database for our LLM to query from. There are a lot of potential improvements in this process including chunking techniques but I hope you now can take any file format and build a RAG pipeline around it. The complete code can be found here.
If you have questions, join our community Slack group to connect with other users, ask questions, share your experiences, and get the latest updates. We can’t wait to see what you’ll build!