Sep 2026· Machine Learning and Knowledge Extraction· 19 references
Abstract
This paper investigates hallucinations in large language models from the perspective of structured extraction, using prompt-based Semantic Role Labeling (SRL) as a controlled case study. SRL requires exact span boundaries and role assignments, while prompting constrained by rationales exposes the reasoning trace associated with each prediction. Our approach employs a DSPy-based pipeline with rule-grounded signatures to show that hallucinations in constrained extraction are systematic, rationale-associated, and thus amenable to targeted mitigation through signature design. Experiments on a representative subset of the CoNLL-2012 dataset show that hallucinations persist even under constrained settings and are systematically associated with failures of rule grounding. Because each prediction is required to cite a single governing rule, errors can be organized and aggregated at the rule level without necessitating additional classification. Leveraging these observations, we introduce a Rationale-Oriented (RO) optimizer that targets such failures by selectively rewriting the relevant parts of the signature. This process mitigates systematic failure modes and leads to measurable improvements in precision, recall, and F1 across multiple evaluation settings, using a representative subset of argument roles aligned with a 5W+1H schema and no model fine-tuning. Signature-perturbation experiments show that cited rules act as diagnostic proxies rather than per-instance causal explanations: the model's parametric priors also contribute to extraction. Even so, rule-level aggregation remains a reliable predictor of where errors occur. These findings suggest that hallucination in structured tasks is closely linked to failures in instruction grounding, and that rule-level feedback and refinement offer a framework for improving reliability in prompt-based systems.
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
The ongoing work building a Raspberry Pi cluster consisting of 300 nodes is presented, with potential use cases being an inexpensive and green test bed for cloud computing research and a robust and mobile data center for operating in adverse environments.
P. Abrahamsson, S. Helmer, Nattakarn Phaphoom et al.· IEEE International Conferenc...· 110 citations· ⚡7
The results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains, and 219 factors representing causes of unhappiness while developing software are identified.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· International Conference on...· 84 citations· ⚡6
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduSep 14, 2026
The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.
AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.