Topic

Knowledge Graph Modeling

All digests tagged Knowledge Graph Modeling

Your company brain will leak secrets: how we stopped it for big banks — Tanmai Gopal, PromptQL thumbnail

· 26:25

Your company brain will leak secrets: how we stopped it for big banks — Tanmai Gopal, PromptQL

The talk addresses the critical security challenge of 'Company Brains'—shared knowledge systems that risk leaking sensitive corporate secrets. The speaker proposes a secure architectural model centered on using a single companywide wiki (linked markdown files) for context storage. Key security measures include scoping read/write access per file, preventing agents from auto-writing memory, and ensuring every change is attributed to a human owner. For multi-user operations, credentials must be injected at the HTTP and SQL layers rather than stored in a sandbox.

Key takeaways

  1. Healthy Company Brain Growth 5:41

    A healthy company brain should show a continuously increasing trend in daily updates, indicating that users are not only consuming knowledge but also teaching the system new skills (e.g., querying data $\rightarrow$ interpreting results $\rightarrow$ taking action).

  2. Secure Knowledge Contribution Model 20:33

    To prevent leakage, context must be stored in a single shared wiki (linked markdown files), and the agent should only *suggest* changes with defined scopes; a human user must accept or reject the change to assign ownership.

  3. Multi-User Security Architecture 25:00

    For collaborative tasks (e.g., incident management), credentials should never be stored in a sandbox. Instead, they must be injected per user at the HTTP and SQL layers to allow the AI agent to behave as the authenticated human.

Watch on YouTube Full article

AI on Your Lakehouse: Context Comes in Shapes, Not Queries — Zach Blumenfeld, Neo4j thumbnail

· 1:59:10

AI on Your Lakehouse: Context Comes in Shapes, Not Queries — Zach Blumenfeld, Neo4j

The presentation introduces a methodology for enhancing AI agent capabilities when querying large lakehouse environments (BigQuery, Databricks, Snowflake). The core argument is that standard vector search or Text2SQL methods often fail due to insufficient global context. The solution involves building three reusable 'graph shapes'—Trees, Communities, and Connections—on top of the data metadata using Neo4j. These shapes create a semantic layer that allows agents to understand complex relationships, patterns, and document hierarchies, enabling them to answer high-level, estate-wide questions.

Key takeaways

  1. Context is in Shapes, Not Queries

    AI agents need more than just data access; they require a structured understanding of how data elements relate. Graph shapes provide this necessary context to prevent the agent from being 'confidently wrong' when dealing with massive datasets.

  2. The Three Core Shapes 10:25

    1) **Trees (Table of Contents):** Provides a containment tree structure for unstructured data, allowing agents to navigate document hierarchies and sections. 2) **Communities (Themes):** Surfaces global, unknown patterns by clustering highly interconnected nodes using algorithms like Leiden. 3) **Connections (Semantic Layer):** Builds a metadata graph over structured warehouse schemas, guiding the agent on how tables join without requiring full ETL.

  3. Agentic Workflow and Tooling 25:00

    The process relies heavily on agents (e.g., Claude Code) utilizing specialized tools like the NeoForj CLY, which allows the agent to write custom Cypher queries based on the provided graph schema/specs.

Watch on YouTube Full article