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
We should create a series of short "Palimpzest Recipes". These will be short 1-2 page documents that show how to accomplish a commonly-wished-for goal.
If PZ is perfect, this is basically a documentation task. But of course PZ probably has a lot of problems, which we will only realize when we try to write the "easy story on how to do X" and realize that we can't do it. So accomplishing this task will sometimes mean just writing a doc, but will often mean doing some design and writing code.
In this case, the Goal is: HOW TO CONSUME A KNOWLEDGE GRAPH.
This is a lot like the How To Use a Database example. The basic idea is that we want to build a RAG-style task where the backing data comes from a source that isn't a RAG system. Instead we want to use information in a Knowledge Graph to answer the user question.
This will be a live KG system, in which we use a service to query the knowledge graph. (The alternative would be one in which the KG has been downloaded and indexed; that can be a good idea, but let's not do that for the moment)
Let's use the Musicbrainz knowledge graph. We should have a system in which:
The system ingests a set of music questions
For each question, we write a Musicbrainz graph query that can answer the question
The graph query is executed and gets some information back
We compose a new prompt that includes the KG information
We answer the new question and give the answer
Part of the challenge in building this system is composing KG queries that are a bit complicated. Like "Who played instrument X on all songs released by artist Y in year Z?"
The text was updated successfully, but these errors were encountered:
We should create a series of short "Palimpzest Recipes". These will be short 1-2 page documents that show how to accomplish a commonly-wished-for goal.
If PZ is perfect, this is basically a documentation task. But of course PZ probably has a lot of problems, which we will only realize when we try to write the "easy story on how to do X" and realize that we can't do it. So accomplishing this task will sometimes mean just writing a doc, but will often mean doing some design and writing code.
In this case, the Goal is: HOW TO CONSUME A KNOWLEDGE GRAPH.
This is a lot like the How To Use a Database example. The basic idea is that we want to build a RAG-style task where the backing data comes from a source that isn't a RAG system. Instead we want to use information in a Knowledge Graph to answer the user question.
This will be a live KG system, in which we use a service to query the knowledge graph. (The alternative would be one in which the KG has been downloaded and indexed; that can be a good idea, but let's not do that for the moment)
Let's use the Musicbrainz knowledge graph. We should have a system in which:
Part of the challenge in building this system is composing KG queries that are a bit complicated. Like "Who played instrument X on all songs released by artist Y in year Z?"
The text was updated successfully, but these errors were encountered: