Knowledge Graph Builder App

In this 3 minute video, Morgan Senechal demonstrates the new Knowledge Graph Builder App.
Full Video: ua-cam.com/users/liveNbyxWAC2TLc
Github: github.com/neo4j-labs/llm-gra...
Neo4j GenAI Ecosystem: neo4j.com/labs/genai-ecosystem/
#neo4j #graphdatabase #llm #knowledgegraph #langchain #openai #pdf #graphrag

[@flor.7797]

glad I don’t have to code this from scratch anymore, thanks

[@AbhishekSharma-wp1lz]

is it a free schema or pre-defined?

[@morgansenechal1434]

Hi @AbhishekSharma-wp1lz , by default the LLM will not use any schema, and will extract entities based on pre-trained knowledge. But if you want to have a specific schema, you can click on the top right setting icon and set your taxonomy. This will be used to create the KG to match exactly your provided taxonomy

[@KostoMax97]

Hello guys,
Does anyone know its possible to keep the layout of the scene frozen when expanding/deleting a node so that the nodes don't get reorder automatically.
Kind regards,
Mario

[@morgansenechal1434]

Hi @KostoMax97 , we do not provide interaction (yet) on the graph visualisation in the LLM KG Builder showcased in this video. So I think you might be referring to another Neo4j tool in your question, you might get better response if you send that question to the community discord or forum with which tools you are using

[@jwolpert]

I'm keen to figure out how to enable a use case where multiple users are entering data and uploading docs, auto-generating nodes/edges/vectors, and then -- this is important -- only being able to query/access their own nodes/edges/vectors. In my use case, it's essential that nobody has acces to anyone else's information. And it's important that the method for this kind of access control is within good auth security practice (no passing uids in the body of an API call). Thoughts? (note -- currently using firebase for auth in my app.)

[@HideBuz]

Just give each user their own database.

[@morgansenechal1434]

As @HideBuz mentioned , the easiest way would be to isolate the data into separated graphs/databases. An alternative tho if you might have users with cross-access (can access different data/needs all in one database) is you can use Neo4j RBAC (Role-Based-Access-Control). this works well with SSO, so you could have your user, creating the KG graph, you would restrict access to the nodes/rel for a role through RBAC. But for it to work, it is important that your Q&A RAG use the SSO user JWT for the retrieval so he only have access to what his role can see