← Latest papers
💻 computer science

ISEE: Interactive Semantic Enrichment for Database Fields

The paper introduces ISEE, an interactive system that collaboratively enriches ambiguous database field descriptions with user domain knowledge to improve LLM agent performance in data-related tasks.

Original authors: Yuan Tian, Yiru Chen, Rakesh R. Menon, Zifan Liu, Ting Cai, Fei Wu, Anudeep Chimakurthi, Prashanthi Ramamurthy, Sridevi Aishwariya Ganesan, Kun Qian, Yunyao Li

Published 2026-08-05
📖 6 min read🧠 Deep dive

Original authors: Yuan Tian, Yiru Chen, Rakesh R. Menon, Zifan Liu, Ting Cai, Fei Wu, Anudeep Chimakurthi, Prashanthi Ramamurthy, Sridevi Aishwariya Ganesan, Kun Qian, Yunyao Li

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

Imagine you are trying to teach a super-smart robot how to understand your messy, complicated notebook. You have a robot that can read almost anything, but it only knows what it learned from the internet. If you write "Python" in your notebook, the robot might think you mean the snake, not the computer language, because it doesn't know your specific context. This is the world of Large Language Models (LLMs): powerful AI tools that act like digital assistants, but they often get stuck when they encounter jargon, abbreviations, or private company secrets that aren't on the public web.

The problem gets worse when these robots try to help you find information in giant databases. Think of a database as a massive library where every book has a label. If the label just says "Value," the robot has no idea if that means "how much money," "how many items," or "how important something is." Without clear labels, the robot can't find the right book, and if it guesses wrong, the whole system breaks. This paper tackles the question: How do we get humans and AI to work together to fix these confusing labels so the robot can actually do its job?

The Problem: The "Lost in Translation" Library

In the real world, companies have databases filled with custom fields. A field might be named "Q3_Sales_Corr" or "User_Active_Flag." To a human expert who built the system, these names make perfect sense. But to an AI, they are a mystery. The AI tries to guess the meaning based on its general training, but when the answer lies in a specific business rule or a private abbreviation, the AI hits a wall. It's like trying to solve a riddle where the key was never written down.

The authors of this paper argue that we can't just rely on the AI to "learn" these secrets on its own, nor can we expect humans to write perfect descriptions from scratch every time. Instead, we need a team-up.

The Solution: ISEE (The Interactive Librarian)

Enter ISEE (Interactive Semantic Enrichment). Think of ISEE as a super-organized, helpful librarian who doesn't just hand you a book, but sits down with you to figure out exactly what you need before you even ask.

Here is how the ISEE system works, broken down into three fun steps:

  1. The "Report Card" (Scoring System):
    First, ISEE looks at the current description of a database field (like "Value") and gives it a report card. It doesn't just say "good" or "bad." It grades the description on five specific things:

    • Usability: Will this help the robot find the right answer?
    • Informativeness: Is it full of useful details, or is it empty?
    • Clarity: Does everyone interpret it the same way?
    • Conciseness: Is it too wordy?
    • Readability: Is it easy to read?
      If the description gets a low score, ISEE tells the human, "Hey, this is confusing! Let's fix it."
  2. The "Detective Questions" (Clarification):
    Instead of asking the human to write a whole new paragraph (which is hard and tiring), ISEE acts like a detective. It asks specific, easy-to-answer questions based on a special list of "clues."

    • Example: If the field is "Python," ISEE might ask, "Are you talking about the snake or the programming language?"
    • Example: If the field is "Laptop," it might ask, "Is this for gaming, school, or work?"
      The human just clicks a button or types a short answer. This is much easier than writing a novel.
  3. The "Guessing Game" (Query Population):
    Sometimes, it's hard to explain a concept with words. So, ISEE tries to guess what the human means by generating example questions.

    • Example: ISEE might say, "Did you mean something like 'What is the average purchase amount per customer'?"
      The human just has to say, "Yes, that's it!" or "No, try something else." This helps the AI understand the purpose of the field without the human having to explain the logic from scratch.

What They Found: The Magic of Teamwork

The researchers tested ISEE in a few different ways to see if it actually worked.

The Human Test:
They invited 8 real experts who work with databases every day. These experts tried to fix confusing field descriptions using three different methods:

  1. Writing the description themselves (Manual Editing).
  2. Picking the best one from a list the AI made (Candidate Selection).
  3. Chatting with a standard AI bot (Conversational AI).
  4. Using the new ISEE system.

The results were clear: ISEE was the winner.

  • The experts felt much less stressed and frustrated using ISEE.
  • When independent judges looked at the final descriptions without knowing who wrote them, the ISEE descriptions were rated much higher (an average score of 6.2 out of 7) compared to the others (which ranged from 3.2 to 4.5).
  • The experts said ISEE improved the accuracy of their work by 119% compared to just editing by hand.

The Robot Simulation:
To see if this would work on a massive scale, the researchers used an AI to simulate a human expert. They fed the system a huge dataset of real-world database questions (1,534 questions from 11 different databases).

  • When the AI tried to answer questions using the original messy descriptions, it got the right answer only about 42% of the time (for finding the right column).
  • When they used the descriptions enriched by the simulated ISEE, the success rate jumped to 64.7%.
  • This suggests that even if the "human" is a robot, the interactive process of asking questions and checking examples makes the data much smarter.

The Real-World Example:
In a specific case study, a field named "Value" was causing trouble. The robot thought it meant the total price of an order, but it actually meant the money from a single transaction.

  • Before ISEE: The robot gave the wrong answer.
  • After ISEE: The human used the system to clarify that "Value" meant "monetary amount per transaction." The description score went from a terrible 18 to a great 82. Suddenly, the robot understood perfectly and gave the correct answer.

The Bottom Line

This paper suggests that we don't need to force humans to write perfect descriptions, nor do we need to wait for AI to magically learn our secrets. Instead, by building a system that scores the current mess, asks simple questions to clear up confusion, and lets humans verify AI guesses, we can make data much easier for robots to understand.

The authors found that this interactive approach significantly reduces the mental effort for humans while making the AI much smarter at tasks like finding the right data or writing code to query it. While the study relied on simulations and a small group of experts, the results strongly suggest that keeping humans in the loop is the key to unlocking the full potential of AI in the workplace.

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 →