GraphNews

This blog post is part of a series that dives into various aspects of SAP’s approach to Generative AI, and its technical underpinnings. In previous blog posts of this series, you learned about how to use large language models (LLMs) for developing AI applications in a trustworthy and reliable manner...

Scientific Data - A semantic approach to mapping the Provenance Ontology to Basic Formal Ontology

Discover how to empower LLM development through effective knowledge graph visualization. Learn to leverage yFiles for intuitive, interactive diagrams that simplify debugging and optimization in AI applications.

A Resource Description Framework (RDF) vocabulary for the Beneficial Ownership Data Standard

🎉🎉 🎉 "Knowledge Graphs Applied" becomes "Knowledge Graphs and LLMs in Action" Four years ago, we embarked on writing "Knowledge Graphs Applied" with a clear mission: to guide practitioners in implementing production-ready knowledge graph solutions. Drawing from our extensive field experience across multiple domains, we aimed to share battle-tested best practices that transcend basic use cases. Like fine wine, ideas, and concepts need time to mature. During these four years of careful development, we witnessed a seismic shift in the technological landscape. Large Language Models (LLMs) emerged not just as a buzzword, but as a transformative force that naturally converged with knowledge graphs.  This synergy unlocked new possibilities, particularly in simplifying complex tasks like unstructured data ingestion and knowledge graph-based question-answering. We couldn't ignore this technological disruption. Instead, we embraced it, incorporating our hands-on experience in combining LLMs with graph technologies. The result is "Knowledge Graphs and LLMs in Action" – a thoroughly revised work with new chapters and an expanded scope. Yet our fundamental goal remains unchanged: to empower you to harness the full potential of knowledge graphs, now enhanced by their increasingly natural companion, LLMs. This book represents the culmination of a journey that evolved alongside the technology itself. It delivers practical, production-focused guidance for the modern era, in which knowledge graphs and LLMs work in concert. Now available in MEAP, with new LLMs-focused chapters ready to be published. #llms #knowledgegraph #graphdatascience

💫 An 𝗲𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝗼𝗻𝘁𝗼𝗹𝗼𝗴𝘆 is just a means, not an end. 👉 Transforming 𝘁𝗮𝗰𝗶𝘁 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 into 𝗲𝘅𝗽𝗹𝗶𝗰𝗶𝘁 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 through an enterprise ontology is a self-contained exercise if not framed within a broader process of knowledge creation, collection, and distribution within the organization. 👇 The 𝗦𝗘𝗖𝗜 𝗠𝗼𝗱𝗲𝗹 effectively describes the various steps of this process, going beyond mere collection and formalization. The SECI model outlines the following four phases that must be executed iteratively and continuously to properly manage organizational knowledge: 1️⃣ 𝗦𝗼𝗰𝗶𝗮𝗹𝗶𝘇𝗮𝘁𝗶𝗼𝗻: In this phase, tacit knowledge is shared through direct interaction, observation, or experiences. It emphasizes the transfer of personal knowledge between individuals and fosters mutual understanding through collaboration (tacit ➡️ tacit). 2️⃣ 𝗘𝘅𝘁𝗲𝗿𝗻𝗮𝗹𝗶𝘇𝗮𝘁𝗶𝗼𝗻: In this phase, tacit knowledge is articulated into explicit forms, such as an enterprise ontology. It helps to codify and communicate the personal knowledge that might otherwise remain unspoken or difficult to share (tacit ➡️ explicit). 3️⃣ 𝗖𝗼𝗺𝗯𝗶𝗻𝗮𝘁𝗶𝗼𝗻: In this phase, explicit knowledge is gathered from different sources, categorized, and synthesized to form new sets of knowledge. It involves the aggregation and reorganization of existing knowledge to create more structured and accessible forms (explicit ➡️ explicit). 4️⃣ 𝗜𝗻𝘁𝗲𝗿𝗻𝗮𝗹𝗶𝘇𝗮𝘁𝗶𝗼𝗻: In this phase, individuals internalize explicit knowledge, turning it back into tacit knowledge through practice, experience, and learning. It emphasizes the transformation of formalized knowledge into personal, actionable knowledge (explicit ➡️ tacit). 🎯 In a world where the only constant is change, it is no longer enough for an organization to know something; what matters most is how fast it learns by creating and redistributing new knowledge internally. 🧑‍🎓 To quote Nadella, organizations and the people within them should not be 𝘒𝘯𝘰𝘸-𝘐𝘵-𝘈𝘭𝘭𝘴 but rather 𝘓𝘦𝘢𝘳𝘯-𝘐𝘵-𝘈𝘭𝘭𝘴. #TheDataJoy #KnowledgeMesh #KnowledgeManagement #Ontologies

Read about how our partners from Semantic Partners explore the latest iteration of the GraphDB's Talk To Your Graph feature

When implementing graph databases in modern software development, we often face a significant challenge: bridging the conceptual gap between ontology-focused knowledge representation and…

Multi-Layer Agentic Reasoning: Connecting Complex Data and Dynamic Insights in Graph-Based RAG Systems 🛜 At the most fundamental level, all approaches rely… | 11 comments on LinkedIn

Build a graph for RAG application for a price of a chocolate bar! What is GraphRAG for you? What is GraphRAG? What does GraphRAG mean from your perspective? What if you could have a standard RAG and a GraphRAG as a combi-package, with just a query switch? The fact is, there is no concrete, universal

In this blog, Ben Kass walks through the minimum requirements to call something a "semantic layer," and how the pieces connect to each other.

🎁⏳ Zep packs Temporal Knowledge Graphs + Semantic Entity Extraction + Cypher Queries storage—Outperforming MemGPT with 94.8% Accuracy. Build Personalized AI… | 46 comments on LinkedIn

Copyright 2025 Kurt Cagle / The Ontologist

To gain competitive advantage from gen AI, enterprises need to be able to add their own expertise to off-the-shelf systems. Yet standard enterprise data stores aren't a good fit to train large language models.

🎉 We're thrilled to unveil Synalinks (🧠🔗), an open-source framework designed to streamline the creation, evaluation, training, and deployment of…

🏆🚣MiniRAG Introduces Near-LLM Accurate RAG for Small Language Models with Just 25% of the Storage. Achieving that by Semantic-Aware Heterogeneous Graph…

I love Markus J. Buehler's work, and his latest paper "Agentic Deep Graph Reasoning Yields Self-Organizing Knowledge Networks" does not disappoint, revealing… | 19 comments on LinkedIn

🏆🚣MiniRAG Introduces Near-LLM Accurate RAG for Small Language Models with Just 25% of the Storage. Achieving that by Semantic-Aware Heterogeneous Graph…

What makes an ontology fail? 9 reasons. At the inauguration of SCOR (Swiss Center for Ontological Research), I had the opportunity to speak alongside Barry… | 154 comments on LinkedIn

🌟 Calling all teachers, students and practitioners in the Semantic Web and knowledge graph community! 🌟 Looking for a fresh, engaging dataset to build… | 18 comments on LinkedIn

Copyright 2025 Kurt Cagle / The Ontologist

Can work on ontologies with Neo4j, including those based on OWL (Web Ontology Language). However, Neo4j alone is not an ontology reasoner.

Breaking LLM Hallucinations in a Smarter Way! (It’s not about feeding more data) Large Language Models (LLMs) still struggle with factual inaccuracies, but…

Build a knowledge graph without an LLM for your RAG applications

Scientific Data - A semantic approach to mapping the Provenance Ontology to Basic Formal Ontology

KET-RAG: Turbocharging AI Agents with 10x Cheaper, Smarter Knowledge Retrieval This Multi-Granular Graph Framework uses PageRank and Keyword-Chunk Graph to have the Best Cost-Quality Tradeoff ﹌﹌﹌﹌﹌﹌﹌﹌﹌ 》The Problem: Knowledge Graphs Are Expensive (and Clunky) AI agents need context to answer complex questions—like connecting “COVID vaccines” to “myocarditis risks” across research papers. But today’s solutions face two nightmares: ✸ Cost: Building detailed knowledge graphs with LLMs can cost $33,000 for a 5GB legal case. ✸ Quality: Cheap methods (like KNN graphs) miss key relationships, leading to 32% worse answers. ☆ Imagine training an AI doctor that either bankrupts you or misdiagnoses patients. Ouch. ﹌﹌﹌﹌﹌﹌﹌﹌﹌ 》The Fix: KET-RAG’s Two-Layer Brain KET-RAG merges precision (knowledge graphs) and efficiency (keyword-text maps) into one system: ✸ Layer 1: Knowledge Graph Skeleton ☆ Uses PageRank to find core text chunks (like “vaccine side effects” in medical docs). ☆ Builds a sparse graph only on these chunks with LLMs—saving 80% of indexing costs. ✸ Layer 2: Keyword-Chunk Bipartite Graph ☆ Links keywords (e.g., “myocarditis”) to all related text snippets—no LLM needed. ☆ Acts as a “fast lane” for retrieving context without expensive entity extraction. ﹌﹌﹌﹌﹌﹌﹌﹌﹌ 》Results: Beating Microsoft’s Graph-RAG with Pennies On HotpotQA and MuSiQue benchmarks, KET-RAG: ✸ Retrieves 81.6% of critical info vs. Microsoft’s 74.6%—with 10x lower cost. ✸ Boosts answer accuracy (F1 score) by 32.4% while cutting indexing bills by 20%. ✸ Scales to terabytes of data without melting budgets. ☆ Think of it as a Tesla Model 3 outperforming a Lamborghini at 1/10th the price. ﹌﹌﹌﹌﹌﹌﹌﹌﹌ 》Why AI Agents Need This AI agents aren’t just chatbots—they’re problem solvers for medicine, law, and customer service. KET-RAG gives them: ✸ Real-time, multi-hop reasoning: Connecting “drug A → gene B → side effect C” in milliseconds. ✸ Cost-effective scalability: Deploying agents across millions of documents without going broke. ✸ Adaptability: Mixing precise knowledge graphs (for critical data) with keyword maps (for speed). Paper in comments ≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣≣ 》Build Your Own Supercharged AI Agent? 🔮 Join My 𝐇𝐚𝐧𝐝𝐬-𝐎𝐧 𝐀𝐈 𝐀𝐠𝐞𝐧𝐭𝐬 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠 TODAY! and Learn Building AI Agent with Langgraph/Langchain, CrewAI and OpenAI Swarm + RAG Pipelines 𝐄𝐧𝐫𝐨𝐥𝐥 𝐍𝐎𝐖 [34% discount]: 👉 https://lnkd.in/eGuWr4CH | 10 comments on LinkedIn

📣Hey Semantic Web/SPARQL/RDF/OWL/Knowledge graph community: Finally! We heard you! I just got this fresh from the dev kitchen: 🎉 Try our free SPARQL query result visualization widget for Jupyter Notebooks! Based on our popular generic graph visualization widget for Jupyter, this widget makes it super convenient to add beautiful graph visualizations of your SPARQL queries to your Jupyter Notebooks. Check out the example notebooks for Google Colab in the GitHub repo https://lnkd.in/e8JP-eiM ✨ This is a pre-1.0-release but already quite capable, as it builds on the well-tested generic widget. We are looking to get your feedback on the features for the final release, so please do take a look and let me know your feedback here, or tell us on GitHub! What features are you missing? What do you like best about the widget? Let me know in the comments and I'll talk to the devs 😊 #sparql #rdf #owl #semanticweb #knowledgegraphs #visualization

I have never been a fan of the "bubble and arrows" kind of graph visualizations. It is generaly useless. But when you can see the entire graph, and can tune the rendering, you start understanding the topology and structure - and ultimately you can tell a story with your graph (and that's what we all love, stories). Gephi is a graph visualization tool to tell these sort of stories with graphs, that has been around for 15 (20 ?) years. Interestingly, while quite a number of Gephi plugins exist to load data (including from neo4j), no decent working plugin exist to load RDF data (yes, there was a "SemanticWebImport" plugin, but it looks outdated, with an old documentation, and does not work with latest - 0.10 - version of Gephi). This doesn't tell anything good for the semantic knowledge graph community. A few weeks ago I literally stumbled upon an old project we developed in 2017 to convert RDF graphs into the GEXF format that can be loaded in Gephi. Time for a serious cleaning, reengineering, and packaging ! So here is a v1.0.0 of the rebranded rdf2gephi utility tool ! The tool runs as a command line that can read an RDF knowledge graph (from files or a SPARQL endpoint), execute a set of SPARQL queries, and turn that into a set of nodes and edges in a GEXF file. rdf2gephi provides default queries to run a simple conversion without any parameters, but most of the time you will want to tune how your graph is turned into GEXF nodes and edges (for example, in my case, `org:Membership` entities relating `foaf:Persons` with `org:Organizations` are not turned into nodes, but into edges, and I want to ignore some other entities). And then what ? then you can load the GEXF file in Gephi, and run a few operations to showcase your graph (see the little screencast video I recorded) : run a layout algorithm, color nodes based on their rdf:type or another attribute you converted, change their size according to the (in-)degree, detect clusters based on a modularity algorithm, etc. etc. - and then export as SVG, PNG, or another format. Also, one of the cool feature supported by the GEXF format are dynamic graphs, where each nodes and edges can be associated to a date range. You can then see your graph evolving through time, like in a movie ! I hope I will be able to tell a more concrete Gephi-powered, RDF-backed graph-story in a future post ! All links in comments.

Bridge the gap and unlock hidden potential within your unstructured data