What changes when you add an agent to GraphRAG? Here's a quick Q&A 🕸️ Agentic GraphRAG: How does an AI agent use a knowledge graph? ❓ How is it different from regular GraphRAG? 💡 The agent gets control of graph retrieval. At runtime it decides where to start, which tool to call, how far to follow relationships, and when it has enough context. ❓ How does it work in practice? 💡 A ReAct loop: check the schema, run a query, observe the result, repeat. "Which other customers hit the same issue?" takes three steps: ・Vector search finds the matching ticket ・A query finds the error the ticket reports ・A query reaches other customers who reported that error ❓ Is it safe to let it write to the graph? 💡 Only if reads and writes are separated. Writes are guarded by narrow permissions, schema checks, confidence thresholds, or human approval. A context graph that stores past decisions and outcomes extends the same idea. ❓ When is it worth building? 💡 When retrieval paths vary by question, the domain keeps changing, or past decisions should inform future ones. Fixed paths are often faster, so start with a working GraphRAG and add autonomy only where it falls short. #GraphRAG# #AIAgents#

Grounding an AI agent's answers in verifiable, explainable facts — an open-source platform offering the full knowledge-graph + GraphRAG + agent stack 🕸️ Title: trustgraph-ai/trustgraph URL: 🕸️ Overview An open-source semantic deployment platform for AI agents. Its core is the "context graph" — a structured, queryable representation of domain knowledge. It delivers the full agentic stack — context graphs, memory, retrieval, orchestration, and inference — for deterministic agent workloads. ❓ Challenges Solved With an LLM alone, it's hard to trace why you got an answer, and hallucination is a risk. ・Grounding an agent's answers in verifiable, explainable facts is difficult ・TrustGraph combines knowledge-graph construction with GraphRAG so agents access context that is semantically rich and verifiable ・And it runs in private deployments with sovereign control 💡 Key Features ・Multi-model DB (tabular, KV, document, graph, vectors) with multimodal support and automated entity/relationship extraction ・DocumentRAG, GraphRAG, and OntologyRAG pipelines, plus 3D GraphViz visualization ・Single/multi-agent with ReAct, Plan-then-Execute, and Supervisor patterns, and MCP integration ・Context Cores: bundle schema, graph, embeddings, evidence, and retrieval policies — versioning context like code 🌍 Tech Stack / Usage Storage on Cassandra, Qdrant, and Garage; messaging via Pulsar and others; LLMs from Anthropic/OpenAI/Google etc. plus local inference (vLLM/Ollama, etc.). Configure via npx @trustgraph/config and use the UI on port 8888. Apache 2.0 licensed. #GraphRAG# #KnowledgeGraph#

"Customer" means one thing to Marketing and another to Finance. What happens when you drop AI agents into a company like that? Agents don't know what business data means. That meaning has traditionally come from code, people's experience and BI tools. When data is fragmented, agents can't even reach the knowledge they need. Neo4j calls this the "agent knowledge problem." Its answer is the Context Engine, built around a six-layer business ontology. Business rules and term definitions, where data lives and who may access it, and runtime knowledge that learns from past decisions are all connected in one graph. Retrieval uses GraphRAG, memory lives in the same graph, and every decision path is tracked. You keep your existing LLM and agent framework. Neo4j Context Engine: Rapidly build dependable enterprise agents It is in private preview, and no performance numbers have been published yet. #Neo4j# #AIAgents#

Join me and 2000 other AI engineers and builders at AI Dev in New York City, Nov 30-Dec 1! A LinkedIn study found that over July-September, the job title AI Engineer has been one of the 10 fastest-growing occupations in seven major economies. AI engineering has become a core skill for all software work, and AI Dev is designed to help you develop it. Our sessions give you hands-on practice with: - Coding agents and harness design: Harness tuning, repository context, autonomous coding - Agent memory and knowledge graphs: GraphRAG, vector search, persistent memory, hybrid retrieval - Agents in production: Evals, observability, simulated testing, browser and voice agents @ylecun and I will also talk about what’s next in world models and physical AI. I hope to see you there! Tickets:

📚 A framework that fixes redundant flat-retrieval RAG by navigating a knowledge graph hierarchically. Title: LeanRAG URL: 📦 Overview LeanRAG is a graph-based RAG framework that combines knowledge graphs with hierarchical retrieval. It was accepted to AAAI 2026. 🔍 The problem it solves Naive retrieval just collects related chunks flatly, leading to overlapping, redundant content and ignoring structural links between documents. LeanRAG traverses semantically aggregated upper layers to produce well-grounded answers with less redundancy. 🛠 The method (5 stages) ・Semantic aggregation: cluster entities into summary nodes with adjacency relations ・Knowledge graph construction: connect entities and summaries in a multi-layer graph ・Hierarchical retrieval: anchor the query at fine-grained entities, then traverse upward to gather evidence ・Redundancy-aware synthesis: streamline overlapping paths ・Generation: an LLM answers from the gathered evidence 📊 Results ・About 46% lower retrieval redundancy versus flat retrieval ・On the Mix benchmark, LeanRAG 8.59 beats HiRAG 8.08, GraphRAG 7.87, and LightRAG 7.61 ・Win rates of 97.3% vs NaiveRAG, 78.1% vs GraphRAG, 81.2% vs LightRAG, and 100% vs FastGraphRAG A compelling option for anyone building a low-redundancy, knowledge-graph-grounded RAG. #RAG# #KnowledgeGraph#

Still shipping your entire schema to a Text-to-SQL agent on every request? You're losing both accuracy and money 💸 Here's how a knowledge graph fixes both. Title: How a Neo4j semantic layer makes your Text-to-SQL agent smarter and cheaper URL: 💸 Overview This post explains how to use a knowledge graph (Neo4j) as a semantic layer to make Text-to-SQL agents both smarter and cheaper. Instead of dumping the full schema every time, the agent retrieves only the subgraph relevant to the question — a GraphRAG approach. ❓ Challenges Solved Most implementations store schema info in static YAML or Markdown and send the whole thing on every request. That creates three serious issues. ・High token cost: transmitting the entire schema repeatedly is expensive ・Contextual noise: irrelevant tables degrade accuracy and trigger hallucinations ・Poor maintainability: flat files go stale as business semantics evolve 💡 Methodology & Proposed Approach The graph stores database structure (schemas, tables, columns, types), constraints, column dictionaries, a business glossary, and usage patterns. The agent retrieves only relevant context in three steps. ・Semantic similarity search: vector indices identify matching columns and terms ・Shortest-path search: find possible joins between identified tables ・Additional context: gather schema definitions, business terms, and sample values Results are formatted as JSON with tables and join paths in milliseconds. 🌍 Use Cases / Experimental Results The post reports improvements that matter directly for production. ・Token reduction: 20-30% on average, up to 10x on simple queries ・Accuracy (multi-table joins): ~98% (Neo4j) vs ~90% (YAML) ・Accuracy (complex CTEs with window functions): ~94% (Neo4j) vs ~85% (YAML) ・Token use scales with complexity (simple ~1,800 / multi-join ~5,000 / advanced ~7,300) The graph captures dynamic usage patterns like join frequencies and behavioral relationships, enabling continuous improvement that static files simply can't model. #TextToSQL# #KnowledgeGraph#

A schema tells you what exists, not what it means. Neo4j has released an open ontology specification as its answer for AI agents 🧭 The Neo4j Ontology Graph Specification: A pragmatic, open, AI-first approach It is an open-source specification for describing domain knowledge in a single machine-readable JSON or YAML file. It is Apache 2.0 licensed, with SDKs for JVM, JavaScript, and Go. Highlights 🛠️ Pragmatic Define nodes, relationships, properties, constraints, and indexes in one file. It validates against a published JSON Schema and fits existing development and operations workflows. 🔗 Interoperable It builds on W3C standards such as RDFS, OWL, SKOS, and SHACL, and documents how RDFS and SHACL concepts map onto the spec. A reference field on every element can link to external standard terms. 🤖 AI-first Descriptions and aliases tell an agent whether "Account" means a bank account, what else it is called, and which identifier (such as an IBAN) applies. One ontology can serve as constraints, data derivation, and agent context. The idea is to write the meaning once and use it in both the database and the agents. There is no RDF serialization yet, and the post includes no performance evaluation. #Neo4j# #GraphRAG#

🕸 Turn text into a "graph of concepts" and use it as a RAG retriever instead of a vector DB. An OSS you can run fully locally. Title: rahulnyk/knowledge_graph URL: 🔍 Overview A project that builds a knowledge graph from unstructured text by extracting concepts (not just named entities) and their relationships, for Graph-Augmented Generation (GRAG) and knowledge-based QA. 🧩 Problem Solved Traditional text analysis struggles to reveal how concepts interconnect and where hidden links lie. Representing knowledge as a queryable graph that preserves meaning enables deeper document understanding. 🛠 Methodology & Approach Built in six steps (clean → extract concepts → extract relations → schema → populate nodes/edges → visualize). Edges carry two weights: W1 for LLM-extracted explicit relations, W2 for same-chunk co-occurrence. Node degree and community set node size and color. 💻 Tech Stack ・LLM: Mistral 7B OpenOrca (no GPT API) ・Serving: Ollama for a fully local pipeline ・Graph: NetworkX, Visualization: Pyvis, Data: Pandas 🎯 Use Cases Graph RAG using the graph as a retriever instead of a vector DB, hidden-link discovery, centrality analysis, and community detection. #KnowledgeGraph# #GraphRAG#

📚 Wouldn't it be great to run ReAct, RAG, and Tree of Thoughts behind one API and compare them, instead of wrangling scattered per-paper implementations? This repo delivers exactly that, with all 35 patterns in one place. Title: FareedKhan-dev/all-agentic-architectures URL: 📦 Overview This is a Python library and a "living textbook" implementing 35 production-grade agentic AI patterns. Every architecture exposes the same .run(task) method and returns an identical result shape, so you can swap patterns without touching downstream code. ❓ Challenges Solved Agentic design patterns have been scattered across papers, each with its own implementation and conventions. The real value here is unifying them under a single interface so you can try them side by side. 💡 Core Idea & Approach The central idea is the "deterministic-picker discipline." ・Instead of handing scoring entirely to the LLM, it first has the LLM commit to categorical features like booleans and enums ・The final decision is then composed in Python logic This mitigates the flat-band pathology of LLM-as-Scorer, and it appears in 13 of the 35 architectures. 🎯 Coverage & Use Cases It spans eight families: reasoning and reflection (Reflection, Self-Discover), search (Tree of Thoughts, LATS), RAG (Corrective/Self/Adaptive/GraphRAG), memory (MemGPT, Voyager), tools and actions (ReAct, SWE-Agent), and multi-agent (Debate, STORM). Each pattern ships with an executed Jupyter notebook, giving reproducible references grounded in real LLM output. 📊 Highlights ・Built on LangGraph, with support for Nebius, OpenAI, Anthropic, Ollama and more, switchable via a single env var ・283 passing pytest tests ・On a 17-task benchmark it recently scored 33/42 correct (78%), with Reflection and Self-Consistency among the strongest #AIAgents# #LangGraph#

📄 Upload your documents, get a knowledge graph — Neo4j's new "Document Intelligence" feature in Aura makes it that simple! Title: Introducing Document Intelligence: From documents to a knowledge graph, right inside Aura URL: 📦 Overview Neo4j has added "Document Intelligence" to its fully managed graph database service Aura. Upload unstructured documents like PDFs, contracts, or technical docs, and the platform automatically extracts entities, resolves duplicates, and constructs a knowledge graph — all without writing a single line of code. ❓ Challenges Solved Most enterprise data is trapped in unstructured documents. Building knowledge graphs from this data previously required complex NLP pipelines, LLM-based entity extraction, entity resolution, and graph schema design — limiting knowledge graph adoption to specialized technical teams. 💡 Methodology & Proposed Approach The feature uses LLM-based entity extraction to identify people, organizations, concepts, and their relationships. Entity resolution merges duplicate references across documents into unified graph nodes. The system infers graph schemas from extracted relationships and stores everything in AuraDB, ready for immediate use with Aura Agent, GenAI Copilot, and GraphRAG pipelines. 🛠 Use Cases - Legal teams automating compliance checks by extracting obligation networks from contract collections - Pharmaceutical companies structuring molecule-disease relationships from clinical trial reports - Enhancing RAG accuracy by supplementing vector search with structural relationships that graphs uniquely capture #KnowledgeGraph# #Neo4j#