Ishigaki-IDS-Bench: A Benchmark for Generating Information Delivery Specification from BIM Information Requirements
This paper introduces Ishigaki-IDS-Bench, a bilingual benchmark comprising 166 expert-verified examples that evaluates the ability of large language models to generate standard-compliant Information Delivery Specification (IDS) XML from Building Information Modeling (BIM) requirements, revealing that current models struggle to consistently satisfy both XML structure and domain vocabulary constraints.
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 Picture: Teaching AI to Speak "Construction Code"
Imagine you are a construction project manager. You have a list of rules written in plain English, like "All walls must be fire-resistant, and the rating must be EI30, EI60, or EI90."
Now, imagine you need to give these rules to a robot builder. But this robot doesn't speak English; it only speaks a very strict, complex computer language called IDS (Information Delivery Specification). This language is like a highly specific dialect of XML that must follow international building standards (IFC) perfectly. If the robot gets even one comma wrong or uses the wrong word for "wall," it won't understand the rule, and the building might be unsafe.
The Problem:
Artificial Intelligence (AI) is great at writing code or JSON files, but it struggles with this specific "construction dialect." It often writes sentences that look like code but contain hidden errors that break the rules.
The Solution (The Paper's Contribution):
The authors created a new "exam" called Ishigaki-IDS-Bench. Think of this as a driving test for AI, but instead of driving a car, the AI has to translate construction rules into perfect, error-free machine code.
How the "Exam" Works
The researchers didn't just throw random text at the AI. They built a high-quality test bank with 166 specific scenarios.
- The Source Material: They took real-world construction scenarios (like "check the pipes" or "verify the steel beams") and wrote them out in both Japanese and English.
- The Answer Key: For every question, human experts (who are like master architects) wrote the perfect computer code answer.
- The Grading System: They didn't just ask a human to read the answers. They used two types of "graders":
- The Syntax Police (IDSAuditTool): This tool checks if the AI's output is grammatically correct. Does it have the right tags? Does it follow the XML rules?
- The Content Detective: This tool compares the AI's answer against the human expert's "Answer Key." Did the AI actually capture the right fire rating? Did it pick the right type of wall?
What Happened When They Tested the AI?
The researchers tested 10 different top-tier AI models (including big names like GPT-5.5 and Claude) on this exam. The results were a bit of a wake-up call:
The "Fake It 'Til You Make It" Problem:
The AI models were very good at looking like they were doing the job. About 95% of the time, the AI produced code that the "Syntax Police" could read. It looked like valid XML.- Analogy: It's like a student who writes a perfect-looking essay with correct spelling and grammar, but the content is completely wrong.
The Reality Check:
When the "Content Detective" checked if the AI actually got the meaning right, the scores dropped hard.- Only about 28% of the AI outputs actually passed the content check.
- Even the best AI model (GPT-5.5) only got a 65.6% score on the final content accuracy.
Where the AI Stumbled:
- The "Vocabulary" Trap: The AI often confused specific construction terms. It might say "wall" when the standard requires a specific code like
IfcWall. - The "Fine Print" Failure: The AI was okay with big ideas but failed at the details, like specific numbers (e.g., EI60 vs. EI90) or complex lists of allowed values.
- Conversation Helps: Interestingly, the AI did much better if it was allowed to have a "conversation" (multi-turn) where it could update its answer based on previous feedback, rather than trying to get it perfect in one single shot.
- The "Vocabulary" Trap: The AI often confused specific construction terms. It might say "wall" when the standard requires a specific code like
Why This Matters (According to the Paper)
The paper argues that we can't just rely on AI to "figure it out" for complex, regulated industries like construction.
- Current State: AI can write some of the rules, but it is not yet reliable enough to generate the final, safety-critical code on its own.
- The Benchmark's Role: This new "exam" (Ishigaki-IDS-Bench) gives researchers a way to measure exactly where the AI fails. Is it failing because it doesn't know the grammar? Or because it doesn't understand the construction vocabulary?
The Takeaway
Think of this paper as a report card for AI in the construction world. It says: "AI is a talented apprentice who can write the rough draft, but it still needs a human master architect to check every single line before it can be used."
The authors have released their "exam questions" and "answer keys" to the public so that other researchers can try to build better AI that can eventually pass this test on its own.
Note on Limitations: The paper explicitly states that this is a diagnostic tool for generating the code, not for validating real-world buildings. The data is based on expert-created scenarios, not leaked real-world confidential projects, and the test focuses on specific parts of the code (entities, attributes, properties), leaving other complex parts for future study.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.