mlsanityData to 14 Oct 2026

Identification of Regulatory Requirements Relevant to Business Processes: A Comparative Study on Generative AI, Embedding-based Ranking, Crowd and Expert-driven Methods

arXiv 2401.02986 ↗First posted 2 Jan 2024cs.CL cs.AIcited by 1

Not on the map. Why?

Abstract (arXiv)

Organizations face the challenge of ensuring compliance with an increasing amount of requirements from various regulatory documents. Which requirements are relevant depends on aspects such as the geographic location of the organization, its domain, size, and business processes. Considering these contextual factors, as a first step, relevant documents (e.g., laws, regulations, directives, policies) are identified, followed by a more detailed analysis of which parts of the identified documents are relevant for which step of a given business process. Nowadays the identification of regulatory requirements relevant to business processes is mostly done manually by domain and legal experts, posing a tremendous effort on them, especially for a large number of regulatory documents which might frequently change. Hence, this work examines how legal and domain experts can be assisted in the assessment of relevant requirements. For this, we compare an embedding-based NLP ranking method, a generative AI method using GPT-4, and a crowdsourced method with the purely manual method of creating relevancy labels by experts. The proposed methods are evaluated based on two case studies: an Australian insurance case created with domain experts and a global banking use case, adapted from SAP Signavio's workflow example of an international guideline. A gold standard is created for both BPMN2.0 processes and matched to real-world textual requirements from multiple regulatory documents. The evaluation and discussion provide insights into strengths and weaknesses of each method regarding applicability, automation, transparency, and reproducibility and provide guidelines on which method combinations will maximize benefits for given characteristics such as process usage, impact, and dynamics of an application scenario.

Key facts. Cited by 1 paper in the map (data through 14 Oct 2026). Builds on 11 of its 53 references that are in the map. First posted on arXiv 2 Jan 2024.

Builds on

11 of 53 references.

References · 11

  1. 2023GPT-4 Technical Reportcited by 18,396
  2. 2019Sentence-BERT: Sentence Embeddings using Siamese BERT-Networkscited by 9,170
  3. 2022Large Language Models are Zero-Shot Reasonerscited by 4,374
  4. 2019How Can We Know What Language Models Know?cited by 959
  5. 2023Is ChatGPT better than Human Annotators? Potential and Limitations of ChatGPT in Explaining Implicit Hate Speechcited by 166
  6. 2022Legal Prompt Engineering for Multilingual Legal Judgement Predictioncited by 55
  7. 2020Leveraging Semantic and Lexical Matching to Improve the Recall of Document Retrieval Systems: A Hybrid Approachcited by 32
  8. 2023Injecting the BM25 Score as Text Improves BERT-Based Re-rankerscited by 17
  9. 2023Just Tell Me: Prompt Engineering in Business Process Managementcited by 17
  10. 2022nigam@COLIEE-22: Legal Case Retrieval and Entailment using Cascading of Lexical and Semantic-based modelscited by 9
  11. 2021DoSSIER@COLIEE 2021: Leveraging dense retrieval and summarization-based re-ranking for case law retrievalcited by 8

Built on by

Cited by year

Citing papers per year: 2025: 1.

1 paper.