← Latest papers
💻 computer science

From Symbolic to Natural-Language Relations: Rethinking Knowledge Graph Construction in the Era of Large Language Models

This position paper argues that the rise of Large Language Models necessitates a paradigm shift in Knowledge Graph construction from rigid, predefined symbolic relation schemas to flexible, context-rich natural-language relation descriptions, supported by hybrid design principles that balance structural integrity with semantic nuance.

Original authors: Kanyao Han, Yushang Lai

Published 2026-01-15
📖 5 min read🧠 Deep dive

Original authors: Kanyao Han, Yushang Lai

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Big Idea: From "Sticky Notes" to "Storytelling"

Imagine you are trying to organize a massive library of information about the world. For a long time, librarians (computer scientists) have used a very strict system: Knowledge Graphs.

In this old system, every piece of information is a "triple" written like a math equation:

[Person A] — [Label] — [Person B]

For example: [Elon Musk] — [works_at] — [Tesla].

The paper argues that this old system is like using tiny, rigid sticky notes to describe complex human relationships. It works well for computers that need simple, clean data, but it throws away all the nuance, context, and "flavor" of real life.

Now, we have Large Language Models (LLMs) (like the AI you are talking to right now). These AIs are amazing at reading and understanding long, detailed stories in natural language. The paper says: Why are we still forcing our knowledge into tiny, rigid sticky notes when our new AI tools are built to read whole novels?

The Problem: The "One-Size-Fits-All" Label

The authors point out three main problems with the old "sticky note" approach:

  1. It's Too Rigid: Real life is messy. Is a relationship between two people "friends"? "Colleagues"? "Rivals"? "Mentor and student"? The old system forces you to pick just one label (like "friend"). If the relationship is complicated, the label lies.
  2. It Loses Context: If you write [John] — [lives_in] — [Paris], you lose the story. Did he move there for love? For a job? Is he visiting for a week or living there forever? The sticky note can't hold that story.
  3. It's Hard for New AI: New AI models are great at reasoning through text. They struggle when forced to look at a graph of disconnected symbols. They prefer reading a sentence like, "John moved to Paris last year to work as a chef," rather than a code like lives_in.

The Solution: Natural Language Relations

The paper proposes a shift. Instead of just using a label like "works_at," we should use natural language descriptions for the connections.

  • Old Way: [Apple] — [founded_by] — [Steve Jobs]
  • New Way: [Apple] — [was founded in 1976 by Steve Jobs in a garage] — [Steve Jobs]

This is like replacing a tiny sticky note with a mini-story.

The Hybrid Approach: The "Skeleton and Flesh"

You might ask: "If we use long stories, won't the computer get lost? Won't it be too messy to search?"

The authors say yes, that is a risk. If you just dump a million unorganized paragraphs, you can't find anything. So, they propose a Hybrid Design:

Think of the Knowledge Graph as a human body:

  • The Skeleton (Symbolic Relations): Keep a few simple, broad labels (like "works_at" or "located_in") to hold the structure together. This helps the computer quickly find the right section of the library.
  • The Flesh (Natural Language): Attach the detailed, rich, natural language stories to those bones. This gives the AI the context it needs to understand the why and how.

This way, the computer can still do fast searches (using the skeleton), but when it needs to think deeply, it reads the rich story (the flesh).

What Needs to Happen Next?

The paper outlines a few challenges for the future, which they call "Research Directions":

  1. Handling Conflicts: What if one source says "John is a friend" and another says "John is a rival"? The new system needs to figure out how to keep both stories without forcing them to merge into one wrong label.
  2. Updating the Skeleton: If the AI reads enough stories and realizes the "friend" label is too vague, we need a way to automatically update the "skeleton" to be more specific.
  3. Better Search: We need new ways to search through these story-filled graphs. Instead of just matching keywords, the AI should be able to "walk" through the graph by reading the stories to find the right path.
  4. New Tests: We can't just check if the computer got the "right" label anymore. We need new ways to test if the AI understood the story correctly.

Summary

The paper is a call to action: Stop forcing the world into rigid boxes.

Because our AI tools have evolved to understand natural language, our way of storing knowledge should evolve too. We should move from a system of discrete labels (like a spreadsheet) to a system of context-rich descriptions (like a library of stories), while keeping just enough structure to keep things organized.

Note on Limitations: The authors admit this is a "position paper," meaning it's a proposal based on logic and existing research, not a report on a finished product they have already built and tested. They also note they focused only on text, not images or audio.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →