Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

1/ The challenges of navigating the vast and complex data landscape are real. Traditional tools often struggle with data overload, lack of effective visualization, and poor customization. ChartGPT is here to solve these challenges. Let's dive deeper 👇

12,735 Aufrufe • vor 3 Jahren •via X (Twitter)

7 Kommentare

Profilbild von CADLabs
CADLabsvor 3 Jahren

2/ Use ChartGPT as your personal data analyst! First, select from one of the sample datasets: - DEX transactions - NFT lending platform aggregate borrow volume - Fastest growing AI & Analytics companies Then, either choose one of the sample questions or come up with your own.

Profilbild von CADLabs
CADLabsvor 3 Jahren

3/ Backend ChartGPT uses @LangChain as a base. This is a library that aims to assist in the development of Large Language Model (LLM) applications. LangChain introduces “agents” which have access to a suite of tools. Depending on the user input, it picks the right tool.

Profilbild von CADLabs
CADLabsvor 3 Jahren

4/ Agent We have created an agent that transforms data into insights by offering an assistance with: - Database connectivity (in our case BigQuery, with plans to expand to other data sources) - SQL generation and data transformation using Pandas - Chart creation using Plotly

Profilbild von CADLabs
CADLabsvor 3 Jahren

5/ LLM and Prompt Engineering We initially started with the @OpenAI gpt-3.5-turbo. After promising results, we included it in our first working prototype. The GPT-4 model, now in testing for the next release, is slower (for now), but delivers more consistent results.

Profilbild von CADLabs
CADLabsvor 3 Jahren

6/ Frontend We used @Streamlit as a frontend, our preferred framework for rapid prototyping. It implements a chatbot interface and allows for a reasonable degree of customization for the first release of the product. Down the line, we plan to build a custom frontend solution.

Profilbild von CADLabs
CADLabsvor 3 Jahren

7/ Are you ready to take your data analytics to the next level? Be the first to experience the power of the ChartGPT assistant! Join the waitlist 👉

Profilbild von CADLabs
CADLabsvor 3 Jahren

8/ Product Hunt We're thrilled to share this journey of data exploration with you, but there's so much more to ChartGPT! We'd love for you to join us in refining and improving our product. Visit our Product Hunt 👉

Ähnliche Videos

Traditional data pipelines don't work for RAG applications. There are 3 issues with them: ​ 1. Traditional data engineering solutions are optimized to handle structured data. RAG applications rely primarily on unstructured data. ​ 2. The connector ecosystem to load data from unstructured data sources is very immature. ​ 3. Traditional solutions do not offer any way to transform unstructured data into an optimized vector search index. ​ The goal of a RAG Pipeline is to solve these problems. ​ The number one objective is to create a reliable vector search index using factual knowledge and relevant context. This sounds easy, but it's one of the biggest challenges we face when building RAG applications. ​ At a high level, there are four different stages in the architecture of a RAG pipeline: ​ 1. Ingestion: Here is where the pipeline loads the information from the data source. ​ 2. Extraction: Where the pipeline processes the input data and decides how to retrieve the text contained inside them. ​ 3. Transform: Where the pipeline chunks the data and generates document embeddings. ​ 4. Load: Where the pipeline creates a search index in a vector database and loads the document embeddings. ​ There are different rabbit holes at each one of these stages. Here are three of them: ​ 1. Ingesting data once is simple. The hard part is refreshing the vector database whenever the original data source changes. ​ 2. Extracting the content of a plain text document is simple. The hard part is to extract content from complex documents containing tables, images, or cross-references. ​ 3. A simple continual chunking strategy with an overlap is simple. The hard part is to find the optimal strategy for your specific knowledge base and the way you are planning to query it. ​ In the attached video, I'll show you how you can build an enterprise-grade RAG Pipeline that solves every one of the above problems. ​ I'll use Vectorize. They partnered with me on this post. You can use them to build RAG pipelines optimized for accurate context retrieval. ​ ​ If you have a few documents lying around, set up a free account and give it a try.

Santiago

40,441 Aufrufe • vor 1 Jahr