🤖 AI Summary
Non-standardized text preprocessing leads to unstable ontology matching (OM) results. Method: We systematically evaluate the impact of a four-stage preprocessing pipeline—tokenization, normalization, stopword removal, and stemming/lemmatization—across 49 OAEI ontology alignment tasks. Our analysis reveals that the first stage (tokenization and normalization) contributes significantly more to matching performance than subsequent stages. Based on this finding, we propose a context-driven preprocessing repair mechanism: (i) dynamically constructing a preservation lexicon to suppress spurious alignments; and (ii) integrating large language models (LLMs) into the pipeline via function calling—bypassing prompt engineering to prevent ground-truth drift. Contribution/Results: Evaluated across eight OAEI tracks, our approach substantially improves matching accuracy and demonstrates robustness. It establishes a reproducible, structured paradigm for synergistic integration of LLMs with classical NLP preprocessing in ontology matching.
📝 Abstract
The generic text preprocessing pipeline, comprising Tokenisation, Normalisation, Stop Words Removal, and Stemming/Lemmatisation, has been implemented in many systems for syntactic ontology matching (OM). However, the lack of standardisation in text preprocessing creates diversity in mapping results. In this paper, we investigate the effect of the text preprocessing pipeline on syntactic OM in 8 Ontology Alignment Evaluation Initiative (OAEI) tracks with 49 distinct alignments. We find that Phase 1 text preprocessing (Tokenisation and Normalisation) is currently more effective than Phase 2 text preprocessing (Stop Words Removal and Stemming/Lemmatisation). To repair the less effective Phase 2 text preprocessing caused by unwanted false mappings, we propose a novel context-based pipeline repair approach that employs an ad hoc check to find common words that cause false mappings. These words are stored in a reserved word set and applied in text preprocessing. The experimental results show that our approach improves the matching correctness and the overall matching performance. We also discuss the integration of the classical text preprocessing pipeline with modern large language models (LLMs). We recommend that LLMs inject the text preprocessing pipeline via function calling to avoid the tendency towards unstable true mappings produced by prompt-based LLM approaches, and use LLMs to repair false mappings generated by the text preprocessing pipeline.