<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>L. Bein)</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Knowledge Graph Reasoning for Intelligent and Explainable Business Process Technologies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Leon Bein</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Technical University of Munich</institution>
          ,
          <addr-line>Bildungscampus 2, 74076 Heilbronn</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0001</lpage>
      <abstract>
        <p>Supporting process executions via software systems is a key concern of the Business Process Management field. With increasing digitization and technological advances, the potential scope of this support shifted and extended, from simply orchestrating tasks following pre-defined routines toward providing comprehensive decision support. However, modern intelligent process support approaches sufer from scattered knowledge bases and black-box technologies, leading to intransparent, hard-to-adapt automated decision making. Knowledge graph technologies appear promising to address this gap. These enriched graph representations of the real world allow for integrative encoding of knowledge of diferent dimensions and performing explainable reasoning thereupon. However, their usage as key driver for business process management systems has not yet been investigated. In this doctoral project, we will investigate the usefulness of knowledge graph technologies for Business Process Management Systems (BPMSs), and design and implement a reference architecture for knowledge-graph-based BPMSs. This research proposal outlines the potentials for using Knowledge Graph technologies for the design of an explainable, deep-knowledge-driven Business Process Management System, provides an overview of existing work, and presents a research outline and the current progress therein.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Business Process Management</kwd>
        <kwd>Knowledge Graphs</kwd>
        <kwd>Prescriptive Process Monitoring</kwd>
        <kwd>Ontology-based Business Process Modeling</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        A key part of the Business Process Management (BPM) field is the support of business process design
and execution using dedicated software systems. These Business Process Management Systems (BPMSs)
support organizations by providing process modeling and monitoring capabilities, as well as
orchestrating their execution by determining, prioritizing, and assigning tasks, managing handovers between
them, and detecting and escalating business errors [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ]. With an increasing digitization of processes
and technological advances, particularly in the umbrella field of Artificial Intelligence (AI), the scope
and applicability of these systems have been steadily widening. A shift in focus, from simply
orchestrating tasks to providing comprehensive decision support hat been observed [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ]. Recent visions of
AI-augmented business process management systems (ABPMS) promise smarter, more autonomous,
and more adaptive orchestration. Among other things, this promises to extend software support to
Knowledge-intensive Processes (KiP) – processes that are driven by expert decisions based on domain
knowledge, exhibiting high variability and need for flexibility [
        <xref ref-type="bibr" rid="ref2 ref3 ref5">2, 5, 3</xref>
        ].
      </p>
      <p>
        To realize this vision, Knowledge Graph (KG) technologies have been identified as a potential key
component [
        <xref ref-type="bibr" rid="ref5 ref6 ref7">5, 6, 7</xref>
        ]. Knowledge Graphs can be defined as data graphs that represent entities and their
relations in a domain of interest, and are extended by context in the form of ontologies, metadata, and
more [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Associated with this notion are a field of research and a toolbox of methods and technologies,
concerned with the elicitation of domain knowledge, its encoding into graphs, and (software-driven)
reasoning thereupon [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>
        Using knowledge graph technologies for business processes can be motivated from multiple angles.
Our motivation is mainly based, first, on the ability of KGs to encode and consequently integrate
knowledge of diferent process perspectives, notably including domain-specific concepts that do not
fall under any common BPM category. This enables a unified management, retrieval, and processing of
the knowledge from these diferent perspectives. Second, the ability of knowledge graph reasoning
methods to jointly consider that knowledge and provide comprehensive explanations [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. These two
capabilities address two key gaps in state-of-the-art process support systems, namely the limiting focus
on knowledge about activities and their relations, and the lack of explainability for decisions made by
current intelligent (neural-net-based) approaches, resulting from this lack of semantic underpinning
and the black-box nature of the employed technologies [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>To realize these potentials, changes to all phases of the interaction with classical BPMS can be
made: For instance, (i) the knowledge stored needs to be extended and shifted from non-uniform
separated representations of activities, goal, organization etc. to a unified process knowledge graph,
(ii) process modeling needs to be extended to more general process knowledge elicitation, and (iii)
strictly following process models or black-box decision making on a shallow knowledge base needs
to be shifted to process-knowledge-graph-based explainable reasoning. We refer to such systems as
Knowledge-graph-based BPMS (KG-BPMS).</p>
      <p>While the potentials of KG-BPMS have been hinted at in previous works (s.a.), the concept has not
been investigated in depth so far. Investigating the realization of KG-BPMSs can shed light on their true
potentials and provide a puzzle piece for advancing the design of ABPMSs. Consequently, this doctoral
project aims to investigate the following overarching questions:
RQ1: How can a business process management system be designed that utilizes knowledge graphs as
primary process knowledge representation and associated technologies for process design and
execution?
RQ2: How do systems following the design perform? What are advantages and challenges of such a
design?</p>
      <p>Using knowledge graphs as main process knowledge representation and associated technologies
as main driver for process design and execution potentially touches upon, and consequently afects,
most aspects of a BPMS. These diferent application potentials synergize, e.g., when using KGs as
main knowledge representation, KG-based reasoning can directly be applied without the need to first
translate the present knowledge. Thus, they can hardly be investigated in full isolation from each other.
Consequently, to adequately assess KG potentials for BPMSs, we plan to investigate a full cross-cut,
i.e., from domain knowledge to decision support. To structure our research, we break this cross-cut
down into several sub-problems to be tackled one after another, informed by the identified potentials
of KG-based BPMS and the common structure of BPMSs: (i) the encoding of process knowledge as
(knowledge) graph, (ii) its elicitation and import into said graph, and (iii) its utilization for process
support.</p>
      <p>In the remainder of this proposal, we first outline the potentials for KG-BPMSs in more detail to
identify the subproblems of interest, outline relevant existing works, and finally present the resulting
work packages and research plan for this project and discuss challenges for the research design.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Potentials for Knowledge Graphs in Business Process Management</title>
    </sec>
    <sec id="sec-3">
      <title>Systems</title>
      <p>
        Rich Integrated Process Encoding A KG-BPMS can integrate the various dimensions of process
knowledge into one uniform data structure, a Process Knowledge Graph (PKG). These dimensions include
(i) common process elements, such as activities and decision points, and their relations (as usually
depicted in, e.g., BPMN or Declare process models), (ii) organizational structure, such as (human)
resources, their roles, permissions, and skills, and resource requirements on activities, (iii) goals and
constraints, often implicitly captured or expressed declaratively (cf. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] for KiP modeling requirements).
Further, notably, a PKG can also integrate knowledge of and about domain-specific concepts that do not
fall under common classifications from the BPM field. For instance, in medical processes, knowledge
about diseases, drugs, symptoms, etc., and their relations is relevant for decision-making. In these cases,
connecting to and reusing existing domain-specific ontologies is promising (cf. [
        <xref ref-type="bibr" rid="ref10 ref11">10, 11</xref>
        ] for examples of
medical ontologies). This way, subsequent querying on and processing is able to consider a rich width
of process knowledge, that is encoded into one integrated structure.
      </p>
      <p>
        In order to achieve this rich, integrated process encoding, an adequate format needs to be found
and respective ontologies (to be extended) engineered. Existing formalisms for the common process
knowledge dimensions can be reused here, e.g., for activity relations and execution history [
        <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
        ], for
organizational knowledge [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], and for goals and constraints [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Further, ways to elicit the process
knowledge need to be investigated. Existing sources of process knowledge, such as human input, event
logs, textual process documentations, process models, regulatory documents, etc., as well as existing
methods, e.g., from the process mining and knowledge graph construction fields, appear promising
to be reused here. Challenges herein lie with transforming the diferent formats into graph form and
ensuring consistency with existing encoded knowledge. We want to highlight here the potential for
Large Language Models (LLMs) for translating textual process descriptions as well as for conversational
knowledge input and conflict resolution.
      </p>
      <p>
        Explainable Prescriptive Process Support Having a process knowledge graph at the ready allows
applying KG-based knowledge retrieval and reasoning techniques on an integrated representation of
the diferent process knowledge dimensions. This yields several promises for the design of BPMSs. First,
to address requirements for designing ABPMSs (cf. [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]) and supporting KiPs (cf. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]). KiP looseness
and variability can be realized by encoding relevant entities and constraints in one structure rather
than relying mainly on activity relationships, such as in BPMN or even Declare, allowing systems to
act more autonomously while considering a well-defined frame. When execution is inherently derived
from goals and constraints rather than routines, adaptation to unexpected events and errors becomes
easier. Process evolution is easier and more comprehensive, as changes only have to be made to the
relevant entities instead of solely to activity relationships.
      </p>
      <p>Second, a KG-BPMS promises more comprehensive decision-making and prescriptive support. This
stems from the availability of explainable graph reasoning approaches (as opposed to black-box process
prediction models) that can utilize the width of process knowledge for their reasoning and
recommendations (as opposed to only providing, e.g., counterfactuals on attributes of an event log).</p>
      <p>Finally, a KG-BPMS can support process participants and owners in providing insight about the
process(es) and their execution. Applying graph knowledge retrieval approaches, allows for explaining,
e.g., where the dependencies of two activities stem from, based on the background process knowledge
encoded in the PKG.</p>
      <p>To achieve explainable prescriptive support first requires the adaptation of existing graph reasoning
approaches to inform a novel kind of process engine. Approaches need to be able to interpret the width
of process knowledge, while at the same time producing comprehensive explanations.</p>
    </sec>
    <sec id="sec-4">
      <title>3. Related Work</title>
      <p>
        Ontology-based Business Process Modeling One of the most important existing streams of BPM
for this project is the field of Ontology-based Business Process Modeling (OBPM), also called Semantic
Business Process Modeling (cp., e.g., [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]). OBPM encompasses approaches to extend classical process
models with instances of ontologies that represent additional background process knowledge, with
the explicit intent to make this knowledge usable for machines [17, 18]. Existing works already allow
expressing BPMN and execution traces as graphs [
        <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
        ], enabling, e.g., checking compliance rules
on process models considering background knowledge [
        <xref ref-type="bibr" rid="ref16">17, 16</xref>
        ]. However, these works are limited to
reasoning at process design-time, and the major focus lies on integrating with existing process modeling
approaches rather than reasoning [18].
      </p>
      <p>
        Knowledge-driven Process Execution Visions and Frameworks Further single key works stand
out to be mentioned because of their relevance for and/or similarity to this work: In their ABPMS
manifesto [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], leading figures of the BPM community introduce the concept and the promised
capabilities. These include framed autonomous execution and adaptation, continuous self-improvement,
and proactive explaining, partially motivating the KG-BPMS potentials presented in this proposal. The
paper names knowledge graphs as one technology to use for internal knowledge representation and
process framing in ABPMSs, without going into detail on how to realize such usage, thus providing a
perfect gap for our work.
      </p>
      <p>
        Similar to our work, Beheshti et al. [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] propose a transformer-architecture-based approach for using a
process knowledge graph to dynamically determine process flow and perform next-activity-prescription.
While their work already provides proposals on how to build the graph (by crowdsourcing) and perform
reasoning on it (using a transformer architecture), it stays at a proposal level.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], Kir and Erdogan present an intelligent BPM framework based on multi-agent systems, and,
notably, ontological modeling. They define diferent aspects to be modeled in the ontology, suggest
existing ontologies to be adopted, and propose to use graph rules for expressing preconditions and
efects of actions, i.e., activities, and for expressing process rules. While their work already gives insight
into what might be relevant aspects of process knowledge and proposes one method for reasoning on
process knowledge graphs (multi-agent systems), it does not contribute to explainable decision support
or give guidance on the elicitation of that knowledge.
      </p>
      <p>To sum up, existing works already suggest and motivate using knowledge graphs for BPM, and
solutions for single problems have been proposed. However, there is a lack of an implemented,
endto-end, knowledge-graph-based BPMS approach that integrates rich process knowledge and provides
explainable execution support.</p>
    </sec>
    <sec id="sec-5">
      <title>4. Research Design &amp; Current Progress</title>
      <p>
        The intended main artifact of this research is a design of a knowledge-graph-based BPMS, intended to
give guidance on the usage of KGs for business process technologies and for evaluating potentials and
challenges. Consequently, as overarching method, we adopt a design-science research (DSR) approach,
as proposed, e.g., by Pefers et al. [ 19] or Hevner et al. [20]. The subchallenges raised in section 2
hereby serve to structure design iterations, each with their own (sub-)objectives and (sub-)evaluation,
feeding into the overall objectives and evaluation and contributing to the overall KG-BPMS design.
Consequently, we define the following work packages:
WP1: Base Architecture As a base and reference for future iteration, the first step in this project is
to develop a base architecture for KG-BPMSs and create a respective base prototype. So far, groundwork
has been done by identifying the potentials of the knowledge graph usage for BPMSs and generating
an initial overview of the dimensions of process knowledge. A respective paper presenting the general
vision has been accepted and presented at the AI4BPM workshop in fall 2024 [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. A simplified draft for
a base architecture is further displayed in Fig. 1, showcasing the envisioned components and interaction
across system boundaries. The development and investigation of the base prototype is in progress, with
a rule-based approach for next-activity prediction as well as a base process knowledge ontology already
in place and a base version of knowledge elicitation yet to be developed.
      </p>
      <p>WP2: Encoding of Process Knowledge An adequate graph format needs to be found and respective
ontologies engineered. Following guidelines from ontology-based process modeling [18], the goal of
this WP is to formalize an initial set of standard process concepts into a base process knowledge graph
design, which organizations can then extend. To this end, we started and will continue to scan and
relate the dimensions of process knowledge described in BPM literature. Rather than iterating, we plan
the insights from the subsequent work packages to continuously seep into this baseline, extending it as
necessary.
Process Knowledge Modeler
Prescription UI
Process Mining
Documentation
…</p>
      <p>Knowledge
Importer</p>
      <p>Process Knowledge</p>
      <p>Graph
Workflows</p>
      <p>Resources
Goals &amp; Constraints</p>
      <p>…</p>
      <p>Domain-Specifics
Knowledge Graph augmented BPMS</p>
      <p>Augmented
Process Engine
WP3: KG-based Process Execution Support Goal of this WP is to investigate the usage of
knowledge graph reasoning techniques for supporting process execution, especially focusing on the
consideration of process knowledge for system decisions and explanations. Specifically, we want to investigate
KGR for (i) next activity prescription and (ii) resource allocation. For this, we plan to transfer and adapt
techniques from Knowledge Graph Reasoning and integrate them with existing BPM paradigms.
Multiple DSR iterations of this work package can be done to improve performance or investigate diferent
avenues of application. A paper outlining a base approach for using a KG-BPMS for resource allocation
has been handed in for review as of writing this proposal.</p>
      <p>WP4: Process Knowledge Elicitation Goal of this WP is to devise methods of “extracting” the
necessary knowledge to fill the process knowledge graph and allow for execution support. Again, we
plan to investigate multiple directions, namely (i) from textual process descriptions, for which we plan
to apply and adapt existing knowledge extraction methods, potentially based on LLMs, (ii) from event
logs and execution data, for which we plan to utilize existing process mining and graph rules mining
methods, and (iii) from process experts directly, for which we envision a conversational user interface.
So far, we have investigated existing graph rules mining methods. Initial insights, however, indicated
poor applicability, motivating the development of tailored solutions.</p>
      <p>WP5: Overall evaluation All of the previous WPs contribute to and inform the design of a final
KG-BPMS and a prototypical implementation thereof. In a final step, we plan to evaluate this overall
artifact, ideally using a real-world industry case, strengthening overall validity by showing feasibility
and utility in organizational settings.
4.1. Research Challenges &amp; Limitations
Due to the cross-cut nature of the planned research, a fine line has to be walked between trying to be
too general, which runs the risk of investigating every area too shallowly, and delving too deeply into
the single sub-problems, which runs the risk of the scope of the project becoming too large. To address
this challenge, we have structured the WPs as described above, focusing on one hand on finishing the
cross-cut before iterating on the same WP, and, on the other hand, investigating each sub-problem as its
own WP, to ensure suficient depth. Further, the current research takes a strongly technology-centered
approach. However, in the same way our proposed changes afect BPMSs in many ways, they also
afect humans involved with the processes. Encoding the knowledge in the system and using it for
reasoning takes agency from the humans, who are thus far the main knowledge holders and decision
makers. This can lead to phenomena such as skill decay, depersonalization, and automation bias [21].
While the scope of this project is suficiently loaded, this important gap motivates future work.</p>
    </sec>
    <sec id="sec-6">
      <title>Declaration on Generative AI</title>
      <p>The author has not employed any Generative AI tools.
Annotated Processes, in: D. Hutchison, T. Kanade, J. Kittler, J. M. Kleinberg, F. Mattern, J. C.
Mitchell, M. Naor, O. Nierstrasz, C. Pandu Rangan, B. Stefen, M. Sudan, D. Terzopoulos, D. Tygar,
M. Y. Vardi, G. Weikum, B. J. Krämer, K.-J. Lin, P. Narasimhan (Eds.), Service-Oriented Computing
– ICSOC 2007, volume 4749, Springer Berlin Heidelberg, Berlin, Heidelberg, 2008, pp. 132–146.
doi:10.1007/978-3-540-89652-4_13.
[17] C. Corea, P. Delfmann, Detecting Compliance with Business Rules in Ontology-Based Process</p>
      <p>Modeling, Wirtschaftsinformatik 2017 Proceedings (2017).
[18] C. Corea, M. Fellmann, P. Delfmann, Ontology-Based Process Modelling - Will We Live to See It?,
in: Conceptual Modeling, Springer, 2021. doi:10.1007/978-3-030-89022-3_4.
[19] K. Pefers, T. Tuunanen, M. Rothenberger, S. Chatterjee, A design science research methodology
for information systems research, Journal of Management Information Systems 24 (2007) 45–77.
doi:10.2753/MIS0742-1222240302.
[20] A. R. Hevner, S. T. March, J. Park, S. Ram, Design Science in Information Systems Research, MIS</p>
      <p>Quarterly 28 (2004) 75. doi:10.2307/25148625.
[21] F. Klessascheck, L. Bein, J. Haase, L. Pufahl, A Critical Investigation of Rationalities in Automation
with BPM, in: 2024 26th International Conference on Business Informatics (CBI), IEEE, 2024, pp.
30–39. doi:10.1109/CBI62504.2024.00014.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. La</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mendling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Reijers</surname>
          </string-name>
          , Fundamentals of Business Process Management, Springer, Berlin, Heidelberg,
          <year>2018</year>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>662</fpage>
          -56509-4.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>H.</given-names>
            <surname>Vu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Leopold</surname>
          </string-name>
          , H. van der Aa,
          <article-title>What is Business Process Automation Anyway?</article-title>
          ,
          <source>in: 56th Hawaii International Conference on System Sciences (HICSS</source>
          <year>2023</year>
          ), ScholarSpace,
          <year>2023</year>
          , pp.
          <fpage>5462</fpage>
          -
          <lpage>5471</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>C.</given-names>
            <surname>Di Ciccio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Marrella</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Russo</surname>
          </string-name>
          ,
          <article-title>Knowledge-Intensive Processes: Characteristics, Requirements and Analysis of Contemporary Approaches</article-title>
          ,
          <source>Journal on Data Semantics</source>
          <volume>4</volume>
          (
          <year>2015</year>
          )
          <fpage>29</fpage>
          -
          <lpage>57</lpage>
          . doi:
          <volume>10</volume>
          . 1007/s13740-014-0038-4.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>H.</given-names>
            <surname>Kir</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Erdogan</surname>
          </string-name>
          ,
          <article-title>A knowledge-intensive adaptive business process management framework</article-title>
          ,
          <source>Information Systems</source>
          <volume>95</volume>
          (
          <year>2021</year>
          )
          <article-title>101639</article-title>
          . doi:
          <volume>10</volume>
          .1016/j.is.
          <year>2020</year>
          .
          <volume>101639</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Fournier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Limonad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Marrella</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Montali</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-R.</given-names>
            <surname>Rehse</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Accorsi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Calvanese</surname>
          </string-name>
          , G. De Giacomo,
          <string-name>
            <given-names>D.</given-names>
            <surname>Fahland</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. La</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Völzer</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Weber</surname>
          </string-name>
          ,
          <source>AI-Augmented Business Process Management Systems: A Research Manifesto, ACM Transactions on Management Information Systems</source>
          <volume>14</volume>
          (
          <year>2023</year>
          )
          <fpage>1</fpage>
          -
          <lpage>19</lpage>
          . doi:
          <volume>10</volume>
          .1145/3576047. arXiv:
          <volume>2201</volume>
          .
          <fpage>12855</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>L.</given-names>
            <surname>Bein</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Pufahl</surname>
          </string-name>
          ,
          <article-title>Knowledge Graphs: A Key Technology for Explainable Knowledge-Aware Process Automation?</article-title>
          ,
          <source>in: Business Process Management Workshops</source>
          , volume
          <volume>534</volume>
          , Springer, Cham,
          <year>2025</year>
          , pp.
          <fpage>18</fpage>
          -
          <lpage>30</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>031</fpage>
          -78666-
          <issue>2</issue>
          _
          <fpage>2</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>A.</given-names>
            <surname>Beheshti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q. Z.</given-names>
            <surname>Sheng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Benatallah</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Casati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Dustdar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. R. M.</given-names>
            <surname>Nezhad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , S. Xue,
          <article-title>ProcessGPT: Transforming Business Process Management with Generative Artificial Intelligence</article-title>
          , in: 2023
          <source>IEEE International Conference on Web Services (ICWS)</source>
          , IEEE, Chicago, IL, USA,
          <year>2023</year>
          , pp.
          <fpage>731</fpage>
          -
          <lpage>739</lpage>
          . doi:
          <volume>10</volume>
          .1109/ICWS60048.
          <year>2023</year>
          .
          <volume>00099</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>A.</given-names>
            <surname>Hogan</surname>
          </string-name>
          , E. Blomqvist,
          <string-name>
            <given-names>M.</given-names>
            <surname>Cochez</surname>
          </string-name>
          , C. d'Amato, G. de Melo,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gutierrez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. E. L.</given-names>
            <surname>Gayo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kirrane</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Neumaier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Polleres</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Navigli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.-C. N.</given-names>
            <surname>Ngomo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. M.</given-names>
            <surname>Rashid</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Rula</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Schmelzeisen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Sequeda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Zimmermann</surname>
          </string-name>
          ,
          <source>Knowledge Graphs, ACM Computing Surveys</source>
          <volume>54</volume>
          (
          <year>2022</year>
          )
          <fpage>1</fpage>
          -
          <lpage>37</lpage>
          . doi:
          <volume>10</volume>
          .1145/3447772. arXiv:
          <year>2003</year>
          .02320.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>A.</given-names>
            <surname>Buliga</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Di Francescomarino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ghidini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. M.</given-names>
            <surname>Maggi</surname>
          </string-name>
          , Counterfactuals and Ways to Build Them:
          <article-title>Evaluating Approaches in Predictive Process Monitoring</article-title>
          ,
          <source>in: Advanced Information Systems Engineering, Lecture Notes in Computer Science</source>
          , Springer, Cham,
          <year>2023</year>
          , pp.
          <fpage>558</fpage>
          -
          <lpage>574</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>031</fpage>
          -34560-9_
          <fpage>33</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>O.</given-names>
            <surname>Bodenreider</surname>
          </string-name>
          ,
          <article-title>The Unified Medical Language System (UMLS): Integrating biomedical terminology</article-title>
          ,
          <source>Nucleic Acids Research</source>
          <volume>32</volume>
          (
          <year>2004</year>
          )
          <fpage>D267</fpage>
          -
          <lpage>D270</lpage>
          . doi:
          <volume>10</volume>
          .1093/nar/gkh061.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>C.</given-names>
            <surname>Ruiz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zitnik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Leskovec</surname>
          </string-name>
          ,
          <article-title>Identification of disease treatment mechanisms through the multiscale interactome</article-title>
          ,
          <source>Nature Communications</source>
          <volume>12</volume>
          (
          <year>2021</year>
          )
          <article-title>1796</article-title>
          . doi:
          <volume>10</volume>
          .1038/s41467-021-21770-8.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>S.</given-names>
            <surname>Bachhofner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Kiesling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Revoredo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Waibel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Polleres</surname>
          </string-name>
          ,
          <source>Automated Process Knowledge Graph Construction from BPMN Models, in: Database and Expert Systems Applications</source>
          , volume
          <volume>13426</volume>
          , Springer, Cham,
          <year>2022</year>
          , pp.
          <fpage>32</fpage>
          -
          <lpage>47</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>031</fpage>
          -12423-
          <issue>5</issue>
          _
          <fpage>3</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>A.</given-names>
            <surname>Annane</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Aussenac-Gilles</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kamel</surname>
          </string-name>
          ,
          <source>BBO: BPMN 2</source>
          .
          <article-title>0 Based Ontology for Business Process Representation</article-title>
          ,
          <source>in: 20th European Conference on Knowledge Management (ECKM</source>
          <year>2019</year>
          ), volume
          <volume>1</volume>
          ,
          <year>2019</year>
          , pp.
          <fpage>49</fpage>
          -
          <lpage>59</lpage>
          . doi:
          <volume>10</volume>
          .34190/KM.19.113.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>M.</given-names>
            <surname>Arias</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Munoz-Gama</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Sepúlveda</surname>
          </string-name>
          ,
          <article-title>Towards a Taxonomy of Human Resource Allocation Criteria</article-title>
          , in: Business Process Management Workshops, volume
          <volume>308</volume>
          , Springer, Cham,
          <year>2018</year>
          , pp.
          <fpage>475</fpage>
          -
          <lpage>483</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -74030-0_
          <fpage>37</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>A.</given-names>
            <surname>Seidel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Haarmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Weske</surname>
          </string-name>
          ,
          <article-title>Model-based decision support for knowledge-intensive processes</article-title>
          ,
          <source>Journal of Intelligent Information Systems</source>
          <volume>61</volume>
          (
          <year>2023</year>
          )
          <fpage>143</fpage>
          -
          <lpage>165</lpage>
          . doi:
          <volume>10</volume>
          .1007/ s10844-022-00770-0.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>C.</given-names>
            <surname>Di Francescomarino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ghidini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Rospocher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Serafini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Tonella</surname>
          </string-name>
          , Reasoning on Semantically
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>