<!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>GT-ARC gGmbH, Ernst-Reuter-Platz</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Towards Automated Human-Centered Recommendation of Explainable AI Solutions⋆</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Nils Ole Breuer</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sahin Albayrak</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>DAI-Labor, Technische Universität Berlin</institution>
          ,
          <addr-line>Ernst-Reuter-Platz 7, 10587 Berlin</addr-line>
        </aff>
      </contrib-group>
      <volume>7</volume>
      <issue>10587</issue>
      <abstract>
        <p>Finding a suitable XAI method from the many XAI possibilities for a specific use case is a non-trivial task. There are recommendation algorithms for recommending XAI methods. However, these are often based solely on the underlying ML model's technical characteristics and do not consider the needs of the target group. Also, these systems often recommend only of-the-shelf XAI methods, frequently failing to achieve the desired explanatory goal. We therefore introduce an automated recommendation framework that tackles both of these problems. On the one hand, we created a low-threshold process in which the needs of the target group can be captured in natural language. On the other hand, we recommend XAI Solutions that include both a suitable XAI method and actionable human-centered design guidelines, which describe how the explanation should be adjusted to be useful for the target group. Our recommendation framework consists of a customized GPT that ofers suitable XAI Solutions based on the given design principles and an XAI database. We evaluate our recommendation framework in two real-world scenarios. The evaluation shows that it can generate human-centered XAI solutions that meet the needs of the target group.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Explainable AI</kwd>
        <kwd>XAI</kwd>
        <kwd>Recommendation framework</kwd>
        <kwd>Interactive explanations</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>The advent of accessible AI technology presents a significant opportunity for individuals without
a technical background to realize their ideas for AI systems. While this democratization of AI
signifies a beneficial advancement, as it fosters the creation of new interdisciplinary AI systems
incorporating a diverse range of ideas, it also introduces risks. At the same time, it emphasizes
the need for explainable and transparent AI. This underlines the central role of explainable AI
(XAI) in ensuring transparency and control.</p>
      <p>Despite the potential benefits of XAI, there are two challenges for applying XAI methods. On
the one hand, it is very dificult to select the most suitable method for a specific use case from
the large and confusing range of XAI methods. On the other hand, of-the-shelf XAI methods
are usually not easily applicable, as explanations for AI systems usually have to be generated in
a very context-specific way and the explanations have to be adapted to the specific target group
Multimodal, Afective and Interactive eXplainable AI Workshop, 27th European Conference on Artificial Intelligence
⋆You can use this document as the template for preparing your publication. We recommend using the latest version
of the ceurart style.
* Corresponding author.
$ nils.breuer@gt-arc.com (N. O. Breuer)</p>
      <p>
        © 2022 Copyright for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).
to be interpretable. Consequently, the laudable intentions to make the AI system as transparent
and explainable as possible usually fail because an unsuitable XAI method was selected or the
target group does not understand the explanation, as the helpfulness in specific use cases is
questionable [
        <xref ref-type="bibr" rid="ref1 ref2 ref3 ref4 ref5 ref6">1, 2, 3, 4, 5, 6</xref>
        ].
      </p>
      <p>
        Our analysis reveals two problem areas in the practical application of XAI methods: first the
selection of an XAI method and second the adaptation of the explanation to a specific target
group. There are solutions for both problem areas. Recommendation algorithms exist to support
the search process for a suitable XAI method. These recommendations are mostly based on
the technical details of the ML model and not on the audience to whom the explanation is
directed [
        <xref ref-type="bibr" rid="ref7 ref8">7, 8</xref>
        ]. Additionally, there is an awareness among researchers in the XAI field that
explanations should be tailored to the audience to be understandable and useful. The research
direction of human-centered XAI (HCXAI) addresses this problem and has already produced
useful concepts [
        <xref ref-type="bibr" rid="ref10 ref11 ref9">9, 10, 11</xref>
        ]. However, these concepts have rarely been formulated as practical
actionable guidelines so that they can be quickly and easily applied for an explanation.
      </p>
      <p>In this work, we aim to connect and address these two problems with a new human-centered
recommendation framework for XAI Solutions. The objective of our recommendation framework
is twofold. First, to enable practitioners without extensive experience in XAI to easily access a
suitable XAI Solution. This requires a low-threshold and interactive process to gather relevant
information. For this, we implemented a natural language-based procedure to collect information
about the target group, i.e., the explainees, and also the technical characteristics of the AI model
to be explained. Second, we want to recommend XAI Solutions which we define not only as an
equivalent for an of-the-shelf XAI method but rather we use the information about the target
group to generate a combination of a suitable XAI method and actionable human-centered
design guidelines that are based on HCXAI concepts to make the explanation as understandable
as possible for the target group. For this, we formulate human-centered design principles based
on theories of HCXAI and social sciences. Additionally, we build an XAI database with the most
relevant XAI methods.</p>
      <p>We create a custom GPT for the recommendation process, using the options provided by
OpenAI’s ChatGPT platform. The custom GPT uses knowledge from our human-centered
design principles and knowledge from our XAI database to recommend a custom XAI Solution
according to our definition.</p>
      <p>
        In summary, our work provides the following contributions:
• We formulate human-centered design principles that are based on socio-cognitive theory
and HCXAI [
        <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
        ] with which explanations of XAI methods can be easily adapted.
• We propose an automated process that allows a wide range of individuals, including
nonXAI-experts to receive recommendations for an XAI Solution for their use case, grounded
in human-centered principles.
• We create a custom GPT that can use pre-defined knowledge to generate customized XAI
      </p>
      <p>Solutions for a specific target group.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <sec id="sec-2-1">
        <title>2.1. Human-Centered XAI (HCXAI)</title>
        <p>
          Many explanations of XAI approaches currently rely on an algorithm-centric perspective and
are therefore based on the intuitions and explanatory objectives of XAI researchers. These
perspectives and explanatory objectives diverge significantly from the requirements of
laypersonfriendly explanations [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. This leads to a dissonance between the theory of XAI methods and
their practical application [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. For this rationale, researchers posit that in crafting explanations
for AI systems, primacy should be accorded to the human recipient for whom the explanation
is intended [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. This concept led to the research field of human-centered XAI (HCXAI).
        </p>
        <p>
          The idea that many HCXAI scientists pursue is that explanations will be more understandable
and useful if they correspond to the social and cognitive processes of human beings. This
humancentered perspective also builds on the article of Miller [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], which examines socio-cognitive
theories and XAI through extensive analysis.
        </p>
        <p>
          HCXAI has developed many theories and principles to date, as can be seen from the sheer
number of recently published articles [
          <xref ref-type="bibr" rid="ref10 ref11 ref16 ref17 ref18 ref9">10, 11, 16, 17, 18, 9</xref>
          ].
        </p>
        <p>
          These theories and principles have already been put into practice in some studies [
          <xref ref-type="bibr" rid="ref19 ref20 ref21 ref22 ref23">19, 20, 21,
22, 23</xref>
          ].
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. XAI Method Recommendation</title>
        <p>
          The problem of selecting a suitable XAI method is ubiquitous in the literature. The usual
approach is to use one of the many available XAI libraries [
          <xref ref-type="bibr" rid="ref24 ref25 ref26">24, 25, 26</xref>
          ] and then select a method
that fits the model architecture. Another option is to make a selection of XAI methods and
then analyze them using technical evaluation methods and select the “best” one [
          <xref ref-type="bibr" rid="ref27 ref8">8, 27</xref>
          ]. These
processes require a high level of expertise and are also demanding for data scientists and
machine learning engineers.
        </p>
        <p>
          Based on interviews with data scientist Retzlaf et al. [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ] introduce a decision tree-based
approach for selecting the most suitable XAI method for a specific use case. The decision tree
enables data scientists to understand the tradeofs between diferent XAI methods and also
shows the user how methods can be combined to ensure the best possible use.
        </p>
        <p>
          One of the few works that aim to automate the recommendation process is the AutoXAI
framework by Cugny et al. [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. In this framework, a user can specify diferent context variables,
technical data about the ML model, and the data set. The XAI Question Bank from Liao et al.
[
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] is then used to select a suitable XAI method. In addition Caro-Martínez et al. [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] created a
holistic platform for the recommendation of personalized XAI experiences based on a case-based
reasoning approach with an ontology. For Caro-Martínez et al. [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] an explanation experience
consists of a solution to an explainability problem and an evaluation of the proposed solution.
        </p>
        <p>
          Studies that focus more on the needs of the target group such as [
          <xref ref-type="bibr" rid="ref30 ref31">30, 31</xref>
          ] ofer helpful analyses
of the target group and also conceptual approaches to what should be considered to recommend
an XAI method in a human-centered way. The actual matching and recommendation process in
these studies are left to future work.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Recommending Human-Centered XAI Solutions</title>
      <p>In this section, we delve deeper into the individual components of our recommendation
framework. First, we explain our human-centered design principles, then discuss how we gather
information about the target group of the XAI solution, how we map this information to XAI
methods, and finally, how the individual components are processed through our
recommendation procedure. Figure 1 shows an overview of all the components of our recommendation
framework.</p>
      <sec id="sec-3-1">
        <title>3.1. Human-Centered Design Principles</title>
        <p>
          As already described in the introduction, existing XAI recommendation algorithms [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] are limited
to simply recommending the raw XAI methods, mostly based on the technical characteristics
of the AI application. Evaluation and user studies have shown that these are often misleading
and do not lead to a causal understanding of the ML model [
          <xref ref-type="bibr" rid="ref1 ref6">1, 6</xref>
          ]. That is why we refer to XAI
Solutions in this paper and not just XAI methods. As stated above we define an XAI Solution as a
comprehensive recommendation that encompasses not only an XAI method but also actionable
human-centered design guidelines, which can be used to tailor the explanation to benefit the
target group, leading to a deep understanding of the behavior of the ML algorithm.
        </p>
        <p>
          From the insights of human-centered XAI research [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] and social sciences [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], we derive
design principles for four categories [
          <xref ref-type="bibr" rid="ref13 ref23 ref32">13, 32, 23</xref>
          ] that are relevant for understanding an
explanation. The design principles are therefore a broad collection of theories, which are then adapted
by the recommender to form actionable guidelines for the explainee target group. The guidelines
for the four categories can then be used to easily tailor the explanation to be more interpretable
for the target group.
        </p>
        <p>
          • Communication. Social science theories indicate that explaining is a form of social
dialogue [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. User studies in the XAI domain also show that explainees primarily seek
some form of social dialogue in explanations or prefer explanations to be supplemented
with verbal descriptions [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
• Interactivity. Studies have shown that the mere presentation of diagrams as explanations
is an obstacle to interpretability, for both experts and non-experts [
          <xref ref-type="bibr" rid="ref33">33</xref>
          ]. Research in HCXAI
indicates that it’s preferable to design explanations for an AI system as an interactive
process in which the behavior of the algorithm can be understood [
          <xref ref-type="bibr" rid="ref34 ref5">5, 34</xref>
          ].
• Selectivity / Complexity. The social sciences have shown that explanations are selective,
which means that the explainer only selects the most important and relevant causes that
are necessary to form an explanation [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. To apply this to explainable AI, a way should
be found to query the needs of the consumer of the explanation before the explanation is
generated in order to select the most important parts of the explanation [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ].
• Customizability. Studies have shown that if the person receiving the explanation has
the opportunity to personalize the explanation to their level of knowledge, mental model,
and preferences, it can have a positive impact on the understanding of the explanation
[
          <xref ref-type="bibr" rid="ref35">35</xref>
          ]. These personalizations could be, on the one hand, that the complexity or the form
of presentation can be adapted independently.
        </p>
        <p>The full design principles for all categories can be found in Appendix A. These design
principles form one of the knowledge files (see Figure 1, blue box) that the recommendation
GPT uses to generate the actionable design guidelines of the XAI Solution.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Background Knowledge and Explanatory Needs of the Target Group</title>
        <p>As can be seen from Figure 1, the recommendation GPT receives information about the
background knowledge and the explanatory needs of the target group as input.</p>
        <p>
          Background Knowledge In many studies where a target group is characterized to create
more personalized explanations, strict stakeholder groups are defined, each with specific needs
for an explanation [
          <xref ref-type="bibr" rid="ref36 ref37">36, 37</xref>
          ]. However, this rigid classification is outdated due to the widespread
use of AI applications in society. Therefore, for our recommendation framework, we use a more
detailed analysis to identify the needs of the target group. To do this, we reference the expertise
definition of [
          <xref ref-type="bibr" rid="ref38">38</xref>
          ], which was adapted within a framework for XAI purposes by [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ]. Following
the framework [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ] we decompose expertise into types of knowledge in specific contexts. The
types of knowledge relate to formal knowledge, e.g. familiarity with theories, instrumental
knowledge, e.g., programming experience, and personal knowledge, e.g., information that a
person knows from the media. To retrieve this information about the explainee group we
formulate open-ended questions that the user of the recommendation framework should answer
in natural language. We provide exemplary answers for each question to guide the answers
in the right direction. All questions can be found in the Appendix B.1. By allowing users
themselves to describe the target group in their language, we generate a much more accurate
description of the target group. However, through our example questions, we still guide them
in a specific direction that aligns with our design principles.
        </p>
        <p>
          Explanatory Needs Further important information about the target group includes the needs
they have for an explanation. Explanatory needs can be divided into tasks that the target group
wants to solve with the explanation and goals that the target group wants to achieve with
an explanation [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ]. Tasks correspond to low-level questions that the target group wants an
answer for, e.g., what features are most important for the ML model? Goals are more high-level
objectives that the target group wants to achieve, e.g., ensure that the ML model complies with
regulations and laws. Just as for the collection of background information, we formulated open
questions that the user of the recommendation framework should answer in their own words.
The questions and sample answers can be found in the Appendix B.2.
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. XAI Database</title>
        <p>In addition to the actionable human-centered design guidelines, XAI methods are also part of
our XAI Solution. For this purpose, we created an XAI database with common XAI methods. The
database defines for each method technical characteristics with which the method is compatible.
Beyond that, we also match goals and tasks to the XAI methods so that the explanatory needs of
the target group can be used to find a suitable XAI method. For example, the above-mentioned
task (What features are most important for the ML model?) is assigned to a feature attribution
method.</p>
      </sec>
      <sec id="sec-3-4">
        <title>3.4. Recommendation Procedure</title>
        <p>Due to the high context specificity, the individual requirements of the target group, and also
the many diferent types of ML models, it is very challenging to create a structured selection
process of XAI methods and human-centered design principles. Many of our attempts with
structural databases failed because we always identified a new use case with a new alternative
ML model in combination with specific requirements of a target group for which no suitable
XAI method in combination with well-founded design guidelines could be found. This is why
we have opted for a more open approach. This approach is reflected in the way the information
is collected, namely in the form of guided free text.</p>
        <p>
          To match the freely formulated explanatory needs and background knowledge of the target
group with actionable human-centered design guidelines and a suitable XAI method from
our XAI database, we utilize the remarkable association possibilities and few-shot learning
capabilities of OpenAI’s large language model GPT-4 [
          <xref ref-type="bibr" rid="ref39">39</xref>
          ]. We create a custom XAI Solution
recommendation GPT. For this, we formulated a detailed instruction prompt explaining the
recommender’s procedure, and also we provided few-shot prompting examples. In Figure 1 it
can be seen that we additionally provide the recommender GPT with two so-called “knowledge
ifles”: Our Human-Centered Design Principles (compare Section 3.1) and our XAI Database
(compare Section 3.3). As can be seen in Figure 1 the recommendation GPT considers the
explanatory needs, and the background knowledge of the target group. Furthermore, it also
uses technical aspects of the ML model if they are mentioned in the answers of the user. Even
though the information retrieval process is structured as a question-answering scheme where
the users of the framework formulate the knowledge and explanatory needs of the target group
by answering questions the recommender GPT does not act as a chat agent. It rather receives all
of the answers of the information retrieval process concatenated as one text section. Based on
that input it then uses the “knowledge files” to generate an individual XAI Solution consisting
of actionable human-centered design guidelines and an XAI method. The detailed instruction
prompt can be found in Appendix C.
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Evaluation of XAI Solutions</title>
      <p>
        We evaluate the capabilities of our recommendation GPT with two use cases. As there is
still no standardized methodology for evaluating the output of LLM, we have evaluated the
XAI solutions of our recommendation GPT in three diferent ways. Human evaluation is still
the gold standard for assessing the quality of LLM output. Because conducting an extensive
human-evaluation study is time-consuming we limited ourselves to a qualitative analysis of the
generated XAI solutions. In addition, we use two automated evaluation metrics to assess the
quality of the design guidelines of the XAI solutions. An embedding-based metric for semantic
textual similarity called SemScore [
        <xref ref-type="bibr" rid="ref40">40</xref>
        ]. And a LLM-based evaluation method called G-Eval [
        <xref ref-type="bibr" rid="ref41">41</xref>
        ].
      </p>
      <sec id="sec-4-1">
        <title>4.1. Use Case 1: Oncology AI</title>
        <p>The first scenario that we analyzed is that of a senior doctor working in the field of oncology.
Recently, the hospital where she works decided to install a new type of AI algorithm to help
detect early breast cancer. However, there are concerns among doctors as they have heard of
other medical algorithms that have also produced negative aspects. The doctors would therefore
like to have an explanation for the algorithm’s decision so that they can evaluate whether the
explanation is flawed and at the same time create confidence in working with the algorithm.
The whole information retrieval process can be viewed in the Appendix D.1 in addition to the
XAI Solution provided by our recommendation GPT. In Figure 2 an excerpt of the information
retrieval process for the formal knowledge of the target group is visualized.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Use Case 2: Extreme Weather AI</title>
        <p>In the second scenario, a group of ML engineers is searching for an explanation for an ML
algorithm with which extreme weather events can be predicted based on climate data. The
problem is that the engineers do not have any formal and instrumental knowledge about the
weather data. Therefore, they want to use the explanation to improve the model and also
understand the climate data in more detail. Again the whole fictive interaction and the XAI
Solution can be found in Appendix D.2. In Figure 3 we visualized the information retrieval
process of the instrumental knowledge and the explanatory needs of the target group.</p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Qualitative Analysis</title>
        <p>The XAI Solution (Appendix D.1, Figure 4) shows that for each of the four explanatory categories,
the recommender GPT gives an actionable design recommendation. The recommendation
follows our definitions and design principles which we extracted from HCXAI research. For
example, the recommendation is to use clear and concise language that integrates medical
terms for the explanation. This corresponds to our rationale for using language as a supporting
medium for visual explanations. This shows that the recommender GPT uses the provided
knowledge file to generate the design recommendation. The selected XAI methods also meet
the needs of the target group. Counterfactual explanation methods are especially often used to
create a causal understanding of an ML model. Since the goal of the explanation for the target
group is to evaluate how trustworthy the algorithm is, a counterfactual explanation fits well, as
it allows decision characteristics to be recognized. These characteristics can then be compared
with the physicians’ medical expertise to decide whether the prediction is trustworthy or not.
From a technical perspective, both recommended XAI methods can also be used for the ML
model.</p>
        <p>As for use case 1 the XAI Solution (Appendix D.2, Figure 5) shows some favorable properties
for use case 2 that are based on the needs and goals of the target group. For example, one goal
is to understand how the model uses climate data to make its prediction. The XAI Solution,
therefore, recommends adding an interactive component to the explanation where the engineers
can construct diferent scenarios and understand how diferent climate features impact the
prediction of the ML model. Additionally, the XAI Solution suggests that the explanation can
use highly specific technical language and statistical concepts because the target group consists
of ML engineers with several years of working experience. Another objective of the target
group is that they want to know which features are most relevant for the ML model, hence
the XAI methods recommended in the XAI Solution are suitable, as two of them are feature
attribution methods.</p>
      </sec>
      <sec id="sec-4-4">
        <title>4.4. Semantic Similarity Evaluation</title>
        <p>
          We also use two automated evaluation metrics so that the evaluation does not depend solely on
our, possibly biased, perception. SemScore [
          <xref ref-type="bibr" rid="ref40">40</xref>
          ] compares the semantic content of a model’s
output and a reference text using embeddings. This method fits well because we want to compare
if the design guidelines confirm our proposed human-centered design principles. SemSocre
computes a correlation value between the embedding of the model output and the reference
text. G-Eval [
          <xref ref-type="bibr" rid="ref41">41</xref>
          ] is a framework that uses Chain-of-Thought prompting to assess the quality of
LLM output based on some evaluation criteria, in our case semantic similarity on a scale from 1
to 5. Meta evaluations show high human alignment values for both metrics.
        </p>
        <p>XXXXXXXMXetrXicX</p>
        <p>Use Case
Oncology AI
Extreme Weather AI</p>
        <p>SemScore</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Discussion</title>
      <p>
        In this study, we embarked on developing a recommendation framework that finds and suggests
human-centered XAI Solutions for individual use cases. For that, we first had to introduce our
notion of XAI Solution which is a combination of conventional XAI methods and actionable
human-centered design guidelines with which these methods can be tailored to a specific target
group. To recommend the design guidelines we formulated human-centered design principles
based on research, drawing on studies from human-centered XAI [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and socio-cognitive
analysis [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. These principles describe how explanations should be created for diferent target
groups so that they are as understandable as possible. Through the formulation of our design
principles, we can recommend actionable guidelines.
      </p>
      <p>
        Because a human-centered XAI Solution is highly individual and context-specific, it is almost
impossible to implement a hard-coded and structured approach with database queries or decision
trees. This conclusion has also been reached by numerous predecessors [
        <xref ref-type="bibr" rid="ref30 ref31 ref7">30, 31, 7</xref>
        ] who have
made the theoretical formulations but were unable to implement a recommendation algorithm.
Hence we decided to utilize the impressive association capabilities of the large language model
GPT-4. We build a customized recommendation GPT that uses among others “knowledge files”
as information bases to generate its recommendation.
      </p>
      <p>We evaluated the results of the recommendation framework for two use cases with three
evaluation metrics. The qualitative analysis of the XAI solutions shows that the recommender GPT is
capable of using the information about the target group to formulate actionable human-centered
design guidelines that correspond to the design principles we formulated. The recommendation
framework grasps the important parts of the target group information and matches it to the
design principles, for example, for the target group ML engineer it recommends that statistical
concepts and machine learning concepts should be used for the explanation. In contrast, for
the target group doctor, it is recommended to avoid technical terms of machine learning but
rather to convey the explanation in medical jargon. Furthermore, if possible, the explanation
should not be centered around ML theories, as the information is not helpful and rather
counterproductive for them. The positive direction suggested by our qualitative analysis is also
backed by the quantitative evaluation metrics. We focused the automated evaluation metrics
on the criteria of semantic similarity. The rationale behind that choice is that we want to
assess whether the generated human-centered design guidelines semantically follow our design
principles, i.e. have the same meaning. The evaluation with both metrics shows positive results
which means that even though both evaluation techniques are based on completely diferent
methodologies our recommendation GPT produces trustworthy actionable design guidelines
which are in agreement with our design principles. Furthermore, we argue that the framework
pays attention to the needs of the target group when selecting a suitable XAI method. In both
of the use cases, the recommender provides suitable help on which XAI method should be used
to achieve the explanatory goal. For example, the group of ML engineer wants to know which
features are most important for the ML model to use this information to improve the ML model.
The recommendation framework rightfully suggests using feature attribution methods that can
provide precisely this information.</p>
      <p>
        Another distinguishing feature of our recommendation framework is that it is language-based.
This opens up the possibility for people who are not necessarily familiar with AI to describe
their needs in their own words. Natural language enables a whole new level of customization
and users can describe their use cases much more precisely than approaches that only ofer a
limited choice for specific use cases [
        <xref ref-type="bibr" rid="ref20 ref42 ref7">7, 20, 42</xref>
        ].
      </p>
      <p>Our recommendation framework thus addresses both issues introduced in the introduction
regarding XAI. It assists in selecting an appropriate XAI method, considering not only the
technical characteristics of the ML model but also selecting the method based on the knowledge
level and explanation goals of the target group. Furthermore, the recommendation framework
provides recommendations and guidelines based on well-established theories of HCXAI, on how
explanations should be tailored to maximize understandability for the target group. To the best
of our knowledge, our approach is the first to integrate these two issues and propose a solution.
Furthermore, unlike any previous methods, our approach ofers unprecedented individuality in
the selection and deployment of XAI methods.</p>
      <p>
        Of course, we are aware of the risks and limitations associated with the use of large language
models [
        <xref ref-type="bibr" rid="ref43 ref44">43, 44</xref>
        ]. We are also aware that it is somewhat contradictory to utilize a type of
ML architecture that is inherently unexplainable for a problem within the domain of XAI.
Nevertheless, we believe that our evaluation approach, combining qualitative human-analysis
which is still considered the gold standard, and automated evaluation metrics could be a way
forward to reliably assess the output of custom GPTs if the possibility for a large-scale expert
survey is not given. Another promising direction for evaluating our recommendation framework
is human-in-the-loop feedback where practitioners provide feedback through conversational
interactions as has been implemented by [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ].
      </p>
      <p>Unfortunately, due to the basic structure and proprietary nature of most large language
models, it cannot be completely ruled out that fatal hallucinations will be generated despite
extensive evaluation. However, we believe that the task to be solved involves such a high
degree of complexity and that a fundamental feature of the framework is the focus on linguistic
exchange that only an LLM is capable of producing satisfactory results.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>In this work, we build a human-centered recommendation framework for XAI Solutions for
specific use cases. Our XAI Solutions consist of a suitable XAI method and actionable
humancentered design guidelines with which the explanation can be tailored for the target group
for better understanding. For this, we build a customized GPT that uses well-defined
humancentered design principles and an XAI database to generate the XAI Solution. The evaluation of
the recommendation framework on two use cases shows that practitioners can overcome two
long-lasting problems in the applications of XAI: first finding a good XAI method and second
making the explanation understandable to the target group.</p>
      <p>There are numerous possibilities for expanding the framework in future work. On the one
hand, we aim to expand the human-centered design principles and incorporate even more
insights from interdisciplinary sciences. On the other hand, the XAI database can be endlessly
expanded with ever-new XAI methods. To make the recommender GPT more robust with larger
datasets, methods like retrieval-augmented generation (RAG) could be employed.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>This work was conducted as part of the Go-KI project (Ofenes Innovationslabor KI zur Förderung
gemeinwohlorientierter KI-Anwendungen), funded by the German Federal Ministry of Labour
and Social Afairs (BMAS) under the funding reference number DKI.00.00032.21.</p>
    </sec>
    <sec id="sec-8">
      <title>A. Human-Centered Design Principles</title>
      <p>This is the content of our knowledge file which the recommender GPT uses to build the XAI
Solution. The knowledge file contains design principles for four explanatory characteristics.
COMMUNICATION From a psychological and philosophical perspective, explanations are a
form of social dialogue. Explanations based solely on visualizations can be hard to interpret.
In addition to just using images and tables, the visual explanation should also be described
verbally, like with text. Moreover, each explanation should be accompanied by some sort of
interpretation guide. This is especially helpful for people who don’t have a high level of formal,
instrumental, and personal knowledge about AI. For AI experts with significant knowledge, the
verbal component isn’t as crucial, but an interpretation guide still improves understanding.
INTERACTIVITY Simply presenting raw visualizations like saliency maps and tabular
explanations does not provide complete understanding. From a social science perspective,
explanations are often viewed as an interactive process. Thus, explanations for a machine learning
model should also be interpreted and structured as an interactive process. This means there
should be a back-and-forth between the explaining medium and the person receiving the
explanation. Through this process, most audiences can gain a reliable mental model of the behavior
of an ML model.</p>
      <p>SELECTIVITY / COMPLEXITY Traditional explanations like saliency maps or tabular
visualizations are often cognitively demanding and can overwhelm people who don’t have
significant formal, instrumental, or personal knowledge because they are too complex. Social
sciences have shown that explanations are selective, meaning the explainer chooses only the
most important and relevant causes to build an explanation. To apply this to explainable AI, a
way should be found to ask for the needs of the explanation consumer before generating the
explanation, allowing the most critical parts to be selected. For example, in feature-importance
methods, not all features should be displayed, just those that are most important or of interest
to the consumer. Similarly, saliency maps can be simplified to make them less complex.
PERSONALIZABILITY Studies have shown that when the recipient of the explanation can
customize it to their knowledge level, mental model, and preferences, it positively impacts
understanding. These personalizations could include adjusting the complexity or presentation
style. However, this should be available only to those with a higher level of AI knowledge.
Simpler personalizations, like changing the color scheme or size, could be ofered to those with
less technical expertise, giving them opportunities to engage with the explanation and better
understand it.</p>
    </sec>
    <sec id="sec-9">
      <title>B. Information retrieval for Background Information and</title>
    </sec>
    <sec id="sec-10">
      <title>Explanatory Needs</title>
      <sec id="sec-10-1">
        <title>B.1. Background Knowledge of the Target Group</title>
        <p>We retrieve the background knowledge and expertise the same way as the explainee needs. We
let the user of the framework describe the knowledge of the target group themselves and just
give initial ideas on what to describe.</p>
        <p>First, we ask if the target group can be categorized into specific stakeholder groups, for example:
• Afected: People who do not actively use the system but are afected by its decisions.
• Users: People who actively use the system.
• Developers: People who implement and build the system
• Owners: People who own the system but not necessarily develop or use it.
• Validators: People who have a supervisory function.</p>
        <p>Second, questions about the formal knowledge of the target group:
• What theoretical/formal knowledge do they have about AI and ML learning, e.g. do they
know the mathematical background of the ML algorithm?
• What theoretical/formal knowledge do they have about the domain in which the ML
model is applied?
• What is the target group’s level of knowledge about similar types of ML algorithms from
the public or from training programs?
Third, questions about the instrumental knowledge of the target group
• What practical knowledge about programming and ML learning does the target group
have?
• Does the target group have practical experience in the domain?
• Does the target group use a lot of AI systems in general?</p>
      </sec>
      <sec id="sec-10-2">
        <title>B.2. Explanatory Needs of the Target Group</title>
        <p>First, the user of the framework can name questions that the target group wants an answer for.
We ask the question: What type of question does the target group of the explanation
want to be answered? and provide some examples of what we mean by the question.
• How reliable is the prediction of the ML model?
• Is the prediction of my ML model faulty/discriminatory/random?
• What information and features does the ML model use to generate the prediction?
• Which factors are particularly important for the output of the ML model?
• What are the limitations of the ML model?
Second the user of the framework can name goals that the target group wants to achieve with
the explanation. Again we first ask the question: What goals should be achieved by the
explanation? and then provide some examples for inspiration.</p>
        <p>• Error detection and improvement of the ML model
• I want to ensure that the ML model complies with regulations and laws
• I want to understand how the ML model can be used for specific tasks
• I want to justify and explain the decisions of the ML model with explanations
• I want to know how the data is utilized
• I want to learn about the knowledge domain in which the model is deployed
• I want to learn how to modify the decisions of the ML model
• I want to create trust through explanation so that users of the ML model have a positive
experience when using it</p>
      </sec>
    </sec>
    <sec id="sec-11">
      <title>C. Recommender GPT Instructions</title>
      <p>The following section is the instruction prompt for the recommender GPT in the OpenAI
ChatGPT platform. The JSON files refer to the design principles 3.1 and the XAI database 3.3:
This GPT is an assistant that gives human-centered XAI recommendations. The recommendation
consists of human-centered design principles which are based on the HCDesignPrinciples.json file
and on XAI Methods which should be from the methods.json file.</p>
      <p>The recommendation for human-centered design principles consists of recommendations in four
characteristics. The recommendation says how explanations should be tailored to a target group
in these four characteristics. The characteristics are communication, interactivity, selectivity,
and customizability. Guidelines for all four characteristics are discussed in the knowledge file
(HCDesignPrinciples.json). Based on these guidelines, recommendations for the four characteristics
will be made for a specific target group.</p>
      <p>The GPT receives answers to questions that describe the knowledge of the target group and also
information about what the explanatory goal of the target group is. Based on this information the
GPT matches the guidelines in the knowledge file (HCDesignPrinciples.json) to the information of
the target group and makes recommendations for all four characteristics on how an explanation
should be adjusted so that it is understandable to the target group.</p>
    </sec>
    <sec id="sec-12">
      <title>D. Use Case Interactions and XAI Solutions</title>
      <sec id="sec-12-1">
        <title>D.1. Use Case 1: Explanation for Doctors</title>
        <sec id="sec-12-1-1">
          <title>Information Retrieval</title>
          <p>Q: For whom are you seeking an explanation for? Describe the target group. Can the target
group be assigned to one of the following categories (Afected, User, Developers, Owners,
Validators)?
A: I am seeking an explanation for doctors at a hospital who are the users of an ML algorithm.
Q: We will now ask you more about the knowledge of the target group. First, we want to know
about the formal knowledge of the target group. What theoretical/formal knowledge do
they have about AI and ML learning, e.g., do they know the mathematical background of
the ML algorithm?
A: The doctors in the hospital do not know anything about AI and ML. Some of them have a
solid mathematical background but in general, they do not know how the ML algorithm
works in theory.</p>
          <p>Q: What theoretical/formal knowledge do they have about the domain in which the ML
model is applied to?
A: The doctors who use the algorithm are well-trained doctors in the domain of oncology
specifically breast cancer.</p>
          <p>Q: What is the target group’s level of knowledge about similar types of ML algorithms from
the public or from training programs?
A: Before the algorithm was used, all users attended an introduction and information event
in which the use of the algorithm was explained.</p>
          <p>Q: Now we will ask about the instrumental knowledge of the target group. What practical
knowledge about programming and ML learning does the target group have?
A: The doctors using the ML system do not have any knowledge about practical programming
or ML learning.</p>
          <p>Q: Does the target group have practical experience in the domain?
A: The target group works as doctors and is experienced in practice.</p>
          <p>Q: Does the target group use a lot of AI systems in general?
A: All users have an average amount of contact with AI in general.</p>
          <p>Q: What type of question does the target group of the explanation want to be answered?
(E.g., How faithful is the prediction of the algorithm? Which features are most important
for the algorithm?)
A: The target group wants to know if the prediction is incorrect and also how trustworthy
the prediction of the algorithm is.</p>
          <p>Q: What goals should be achieved by the explanation?
A: The goal is to use the explanation to build trust among the doctors using the algorithm
but also to justify the decision that we make based on the algorithm’s prediction.</p>
        </sec>
      </sec>
      <sec id="sec-12-2">
        <title>D.2. Use Case 2: Explanation for ML Engineers</title>
        <sec id="sec-12-2-1">
          <title>Information Retrieval</title>
          <p>Q: For whom are you seeking an explanation for? Describe the target group. Can the target
group be assigned to one of the following categories (Afected, User, Developers, Owners,
Validators)?
A: The target group is ML Engineers working at an AI software company that is implementing
an ML algorithm.</p>
          <p>Communication The explanation should employ
clear, concise language that integrates medical
terminology familiar to oncologists with basic
statistical concepts to explain the algorithm's
outputs. Use of visual aids like graphs or charts to
show statistical reliability (like confidence intervals or
prediction probabilities) can be helpful. Since the
doctors have attended an introductory event, the
explanation can build on the foundational knowledge
they already possess about the algorithm’s intended
use, focusing on practical application rather than
theoretical aspects
Selectivity / Complexity The explanation should
selectively focus on aspects of the algorithm that
directly relate to clinical decision-making in oncology.</p>
          <p>This might include an emphasis on the most
significant features the algorithm considers when
making a prediction, such as tumor size, type, and
location, and how these are weighted within the
model. Presenting simplified case studies where the
algorithm's predictions were particularly successful,
as wel as scenarios where it was less accurate, can
il ustrate its performance spectrum in a clinical y
relevant manner.</p>
          <p>Counterfactual Explanations: This method would al ow doctors to see how altering certain input
variables (like changing a measurement or condition slightly) could lead to different predictions. This is
particularly useful for understanding edge cases or close-cal decisions made by the algorithm.</p>
          <p>Feature Importance: Methods like SHAP (SHapley Additive exPlanations) can elucidate which features
are most influential in the algorithm’s predictions. This aligns wel with a need to understand and trust the
predictive factors, especial y in complex cases of breast cancer diagnosis.</p>
          <p>These explanations, tailored to the needs and backgrounds of the doctors, aim to enhance their trust in the AI system by making its
operations transparent and directly relevant to their clinical practice. This approach should also aid in justifying clinical decisions
influenced by the algorithm's predictions, ensuring that the tool is a valuable asset to the oncological team.
the ML algorithm?
and ML learning algorithms.
model is applied to?
general. We only use the data.
the public or from training programs?
We will now ask you more about the knowledge of the target group. First, we want to know
about the formal knowledge of the target group. What theoretical/formal knowledge do
they have about AI and ML learning, e.g., do they know the mathematical background of
We are all ML Engineers and have extensive knowledge about the theory behind most AI
Q: What theoretical/formal knowledge do they have about the domain in
which the</p>
          <p>ML
A: The algorithm that we are implementing is concerned with predicting extreme weather
events from climate data. We do not have knowledge about meteorology and climate in
Q: What is the target group’s level of knowledge about similar types of ML algorithms from
We researched similar algorithms online that also use climate data to predict extreme
weather events.</p>
          <p>Now</p>
          <p>we will ask about the instrumental knowledge of the target group. What practical
knowledge about programming and ML learning does the target group have?</p>
          <p>Communication Given the target group’s extensive
knowledge in ML, the explanations can use technical
language, incorporating advanced statistical and
machine learning concepts. However, since the
engineers are not familiar with meteorology, it’s
crucial to clearly define any meteorological terms and
concepts used in the model. Visual aids like
advanced data visualizations that map climate data
inputs to prediction outputs can be beneficial.</p>
          <p>Documentation or tooltips that provide brief
explanations of meteorological terms and their
relevance to the model’s predictions can enhance
understanding.</p>
          <p>Interactivity An interactive explanation interface
would be highly beneficial for this group. It could
al ow engineers to manipulate input data points and
observe how these changes affect the model’s
predictions. Tools that enable them to test model
behavior under various synthetic scenarios they
construct can deepen their understanding of how
different climate features influence predictions. This
interactive process facilitates a practical exploration
of the model's behavior, providing insights that are
crucial for both trust and model refinement.</p>
          <p>Customizability Providing options to customize the
level of detail in the explanations would cater to
individual preferences within the group. Some
engineers might prefer a high-level overview of model
performance metrics, while others might delve into
the nuances of algorithmic decisions and data usage.</p>
          <p>Al owing engineers to choose the complexity of the
information presented or to toggle between a basic
and advanced view of explanations could enhance
usability and engagement.
are.</p>
          <p>We are all experienced ML engineers with several years of working experience.
Q: Does the target group have practical experience in the domain?
A: No, we do not have any knowledge about meteorology.</p>
          <p>Q: Does the target group use a lot of AI systems in general?</p>
          <p>We are very proficient with AI systems and frequently use them in our daily lives.
Q: What type of question does the target group of the explanation want to be answered?
(E.g., How faithful is the prediction of the algorithm? Which features are most important
We want to learn the behavior of the model and want to know
which features are most
important for the ML model. We also want to know what the limitations of the ML model
Q: What goals should be achieved by the explanation?
A:</p>
          <p>We want to improve the ML model by knowing the behavior of the model and additionally,
we want to know how the data is used by the ML model.</p>
        </sec>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>H.</given-names>
            <surname>Vasconcelos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Jörke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Grunde-McLaughlin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Gerstenberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. S.</given-names>
            <surname>Bernstein</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Krishna</surname>
          </string-name>
          ,
          <article-title>Explanations can reduce overreliance on ai systems during decision-making</article-title>
          ,
          <source>Proceedings of the ACM on Human-Computer Interaction</source>
          <volume>7</volume>
          (
          <year>2023</year>
          )
          <fpage>1</fpage>
          -
          <lpage>38</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>C.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Feng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sharma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <article-title>Machine explanations and human understanding (</article-title>
          <year>2022</year>
          ), URL: http://arxiv. org/abs/2202.04092 (
          <year>2022</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>S. S.</given-names>
            <surname>Kim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Meister</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V. V.</given-names>
            <surname>Ramaswamy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Fong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Russakovsky</surname>
          </string-name>
          ,
          <article-title>Hive: Evaluating the human interpretability of visual explanations</article-title>
          ,
          <source>in: European Conference on Computer Vision</source>
          , Springer,
          <year>2022</year>
          , pp.
          <fpage>280</fpage>
          -
          <lpage>298</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>R. S.</given-names>
            <surname>Zimmermann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Borowski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Geirhos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Bethge</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Wallis</surname>
          </string-name>
          , W. Brendel,
          <article-title>How well do feature visualizations support causal understanding of cnn activations?</article-title>
          ,
          <source>Advances in Neural Information Processing Systems</source>
          <volume>34</volume>
          (
          <year>2021</year>
          )
          <fpage>11730</fpage>
          -
          <lpage>11744</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>A.</given-names>
            <surname>Bertrand</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Viard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Belloum</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. R.</given-names>
            <surname>Eagan</surname>
          </string-name>
          , W. Maxwell,
          <article-title>On selective, mutable and dialogic xai: a review of what users say about diferent types of interactive explanations</article-title>
          ,
          <source>in: Proceedings of the 2023 CHI Conference on Human Factors in Computing Systems</source>
          ,
          <year>2023</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>21</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>J.</given-names>
            <surname>Adebayo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Gilmer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Muelly</surname>
          </string-name>
          , I. Goodfellow,
          <string-name>
            <given-names>M.</given-names>
            <surname>Hardt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Kim</surname>
          </string-name>
          ,
          <article-title>Sanity checks for saliency maps</article-title>
          ,
          <source>Advances in neural information processing systems</source>
          <volume>31</volume>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>R.</given-names>
            <surname>Cugny</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Aligon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Chevalier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. Roman</given-names>
            <surname>Jimenez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Teste</surname>
          </string-name>
          ,
          <article-title>Autoxai: A framework to automatically select the most adapted xai solution</article-title>
          ,
          <source>in: Proceedings of the 31st ACM International Conference on Information &amp; Knowledge Management</source>
          ,
          <year>2022</year>
          , pp.
          <fpage>315</fpage>
          -
          <lpage>324</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>P.</given-names>
            <surname>Bommer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kretschmer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Hedström</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Bareeva</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. M.-C. Höhne</surname>
          </string-name>
          ,
          <article-title>Finding the right xai method-a guide for the evaluation and ranking of explainable ai methods in climate science</article-title>
          ,
          <source>arXiv preprint arXiv:2303.00652</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>K.</given-names>
            <surname>Sokol</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Flach</surname>
          </string-name>
          ,
          <article-title>One explanation does not fit all: The promise of interactive explanations for machine learning transparency</article-title>
          ,
          <source>KI-Künstliche Intelligenz</source>
          <volume>34</volume>
          (
          <year>2020</year>
          )
          <fpage>235</fpage>
          -
          <lpage>250</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>U.</given-names>
            <surname>Ehsan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. O.</given-names>
            <surname>Riedl</surname>
          </string-name>
          ,
          <article-title>Human-centered explainable ai: Towards a reflective sociotechnical approach</article-title>
          ,
          <source>in: HCI International 2020-Late Breaking Papers: Multimodality and Intelligence: 22nd HCI International Conference, HCII 2020</source>
          , Copenhagen, Denmark,
          <source>July 19-24</source>
          ,
          <year>2020</year>
          , Proceedings 22, Springer,
          <year>2020</year>
          , pp.
          <fpage>449</fpage>
          -
          <lpage>466</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>Q. V.</given-names>
            <surname>Liao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. R.</given-names>
            <surname>Varshney</surname>
          </string-name>
          ,
          <article-title>Human-centered explainable ai (xai): From algorithms to user experiences</article-title>
          ,
          <source>arXiv preprint arXiv:2110.10790</source>
          (
          <year>2021</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>T.</given-names>
            <surname>Miller</surname>
          </string-name>
          ,
          <article-title>Explanation in artificial intelligence: Insights from the social sciences</article-title>
          ,
          <source>Artificial intelligence 267</source>
          (
          <year>2019</year>
          )
          <fpage>1</fpage>
          -
          <lpage>38</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>K.</given-names>
            <surname>Sokol</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Flach</surname>
          </string-name>
          ,
          <article-title>Explainability fact sheets: A framework for systematic assessment of explainable approaches</article-title>
          ,
          <source>in: Proceedings of the 2020 conference on fairness, accountability, and transparency</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>56</fpage>
          -
          <lpage>67</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>H.</given-names>
            <surname>Shen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.-H.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <article-title>How useful are the machine-generated interpretations to general users? a human evaluation on guessing the incorrectly predicted labels</article-title>
          ,
          <source>in: Proceedings of the AAAI Conference on Human Computation and Crowdsourcing</source>
          , volume
          <volume>8</volume>
          ,
          <year>2020</year>
          , pp.
          <fpage>168</fpage>
          -
          <lpage>172</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>M.</given-names>
            <surname>Ribera</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Lapedriza</surname>
          </string-name>
          ,
          <article-title>Can we do better explanations? a proposal of user-centered explainable ai</article-title>
          ,
          <source>CEUR Workshop Proceedings</source>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>Q. V.</given-names>
            <surname>Liao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Pribić</surname>
          </string-name>
          , J. Han,
          <string-name>
            <given-names>S.</given-names>
            <surname>Miller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Sow</surname>
          </string-name>
          ,
          <article-title>Question-driven design process for explainable ai user experiences</article-title>
          ,
          <source>arXiv preprint arXiv:2104.03483</source>
          (
          <year>2021</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>H.</given-names>
            <surname>Lakkaraju</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Slack</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Singh</surname>
          </string-name>
          ,
          <article-title>Rethinking explainability as a dialogue: A practitioner's perspective</article-title>
          ,
          <source>arXiv preprint arXiv:2202</source>
          .
          <year>01875</year>
          (
          <year>2022</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>A.</given-names>
            <surname>Holzinger</surname>
          </string-name>
          , G. Langs,
          <string-name>
            <given-names>H.</given-names>
            <surname>Denk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Zatloukal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Müller</surname>
          </string-name>
          ,
          <article-title>Causability and explainability of artificial intelligence in medicine</article-title>
          ,
          <source>Wiley Interdisciplinary Reviews: Data Mining and Knowledge Discovery</source>
          <volume>9</volume>
          (
          <year>2019</year>
          )
          <article-title>e1312</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>M.</given-names>
            <surname>Chromik</surname>
          </string-name>
          ,
          <article-title>Making shap rap: Bridging local and global insights through interaction and narratives, in: Human-Computer Interaction-INTERACT</article-title>
          <year>2021</year>
          :
          <article-title>18th IFIP TC 13 International Conference</article-title>
          , Bari, Italy,
          <source>August 30-September 3</source>
          ,
          <year>2021</year>
          , Proceedings,
          <source>Part II 18</source>
          , Springer,
          <year>2021</year>
          , pp.
          <fpage>641</fpage>
          -
          <lpage>651</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>D.</given-names>
            <surname>Slack</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Krishna</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Lakkaraju</surname>
          </string-name>
          ,
          <string-name>
            <surname>S. Singh,</surname>
          </string-name>
          <article-title>Explaining machine learning models with interactive natural language conversations using talktomodel</article-title>
          ,
          <source>Nature Machine Intelligence</source>
          <volume>5</volume>
          (
          <year>2023</year>
          )
          <fpage>873</fpage>
          -
          <lpage>883</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Pi</surname>
          </string-name>
          ,
          <string-name>
            <surname>Infeature:</surname>
          </string-name>
          <article-title>An interactive feature-based-explanation framework for non-technical users</article-title>
          , in: International Conference on Human-Computer Interaction, Springer,
          <year>2023</year>
          , pp.
          <fpage>262</fpage>
          -
          <lpage>273</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>V.</given-names>
            <surname>Lai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q. V.</given-names>
            <surname>Liao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <article-title>Selective explanations: Leveraging human input to align explainable ai</article-title>
          ,
          <source>arXiv preprint arXiv:2301.09656</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>X.</given-names>
            <surname>Kong</surname>
          </string-name>
          , S. Liu,
          <string-name>
            <given-names>L.</given-names>
            <surname>Zhu</surname>
          </string-name>
          ,
          <article-title>Toward human-centered xai in practice: A survey</article-title>
          ,
          <source>Machine Intelligence Research</source>
          (
          <year>2024</year>
          )
          <fpage>1</fpage>
          -
          <lpage>31</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>N.</given-names>
            <surname>Kokhlikyan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Miglani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Martin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Alsallakh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Reynolds</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Melnikov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Kliushkina</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Araya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Yan</surname>
          </string-name>
          , et al.,
          <article-title>Captum: A unified and generic model interpretability library for pytorch</article-title>
          , arXiv preprint arXiv:
          <year>2009</year>
          .
          <volume>07896</volume>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>A.</given-names>
            <surname>Saucedo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>U.</given-names>
            <surname>Iqbal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Krishna</surname>
          </string-name>
          ,
          <article-title>Xai-an explainability toolbox for machine learning</article-title>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>V.</given-names>
            <surname>Arya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. K. E.</given-names>
            <surname>Bellamy</surname>
          </string-name>
          , P.-Y. Chen,
          <string-name>
            <given-names>A.</given-names>
            <surname>Dhurandhar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Hind</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. C.</given-names>
            <surname>Hofman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Houde</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q. V.</given-names>
            <surname>Liao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Luss</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Mojsilović</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Mourad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Pedemonte</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Raghavendra</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Richards</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Sattigeri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Shanmugam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Singh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. R.</given-names>
            <surname>Varshney</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Wei</surname>
          </string-name>
          ,
          <string-name>
            <surname>Y. Zhang,</surname>
          </string-name>
          <article-title>One explanation does not fit all: A toolkit and taxonomy of ai explainability techniques</article-title>
          ,
          <year>2019</year>
          . URL: https: //arxiv.org/abs/
          <year>1909</year>
          .03012.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>A.</given-names>
            <surname>Perotti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Borile</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Miola</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. P.</given-names>
            <surname>Nerini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Baracco</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Panisson</surname>
          </string-name>
          , Explainability, quantified: Benchmarking xai techniques,
          <source>in: World Conference on Explainable Artificial Intelligence</source>
          , Springer,
          <year>2024</year>
          , pp.
          <fpage>421</fpage>
          -
          <lpage>444</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>C. O.</given-names>
            <surname>Retzlaf</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Angerschmid</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Saranti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Schneeberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Roettger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Mueller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Holzinger</surname>
          </string-name>
          ,
          <article-title>Post-hoc vs ante-hoc explanations: xai design guidelines for data scientists</article-title>
          ,
          <source>Cognitive Systems Research</source>
          (
          <year>2024</year>
          )
          <fpage>101243</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>M.</given-names>
            <surname>Caro-Martínez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Recio-García</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Díaz-Agudo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Darias</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Wiratunga</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Martin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Wijekoon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Nkisi-Orji</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Corsar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Pradeep</surname>
          </string-name>
          , et al.,
          <article-title>isee: A case-based reasoning platform for the design of explanation experiences, Knowledge-Based Systems (</article-title>
          <year>2024</year>
          )
          <fpage>112305</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>T.</given-names>
            <surname>Vermeire</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Laugel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Renard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Martens</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Detyniecki</surname>
          </string-name>
          ,
          <article-title>How to choose an explainability method? towards a methodical implementation of xai in practice</article-title>
          ,
          <source>in: Joint European Conference on Machine Learning and Knowledge Discovery in Databases</source>
          , Springer,
          <year>2021</year>
          , pp.
          <fpage>521</fpage>
          -
          <lpage>533</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>H.</given-names>
            <surname>Suresh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. R.</given-names>
            <surname>Gomez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. K.</given-names>
            <surname>Nam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Satyanarayan</surname>
          </string-name>
          ,
          <article-title>Beyond expertise and roles: A framework to characterize the stakeholders of interpretable machine learning and their needs</article-title>
          ,
          <source>in: Proceedings of the 2021 CHI Conference on Human Factors in Computing Systems</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>16</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <given-names>T. A.</given-names>
            <surname>Schoonderwoerd</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Jorritsma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Neerincx</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Van Den</surname>
          </string-name>
          <string-name>
            <surname>Bosch</surname>
          </string-name>
          ,
          <article-title>Human-centered xai: Developing design patterns for explanations of clinical decision support systems</article-title>
          ,
          <source>International Journal of Human-Computer Studies</source>
          <volume>154</volume>
          (
          <year>2021</year>
          )
          <fpage>102684</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>H.</given-names>
            <surname>Kaur</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Nori</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Jenkins</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Caruana</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Wallach</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. Wortman</given-names>
            <surname>Vaughan</surname>
          </string-name>
          ,
          <article-title>Interpreting interpretability: understanding data scientists' use of interpretability tools for machine learning</article-title>
          ,
          <source>in: Proceedings of the 2020 CHI conference on human factors in computing systems</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>14</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          [34]
          <string-name>
            <given-names>M.</given-names>
            <surname>Chromik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Butz</surname>
          </string-name>
          ,
          <article-title>Human-xai interaction: a review and design principles for explanation user interfaces</article-title>
          ,
          <source>in: Human-Computer Interaction-INTERACT</source>
          <year>2021</year>
          :
          <article-title>18th IFIP TC 13 International Conference</article-title>
          , Bari, Italy,
          <source>August 30-September 3</source>
          ,
          <year>2021</year>
          , Proceedings,
          <source>Part II 18</source>
          , Springer,
          <year>2021</year>
          , pp.
          <fpage>619</fpage>
          -
          <lpage>640</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          [35]
          <string-name>
            <given-names>J.</given-names>
            <surname>Schneider</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Handali</surname>
          </string-name>
          ,
          <article-title>Personalized explanation in machine learning: A conceptualization</article-title>
          , arXiv preprint arXiv:
          <year>1901</year>
          .
          <volume>00770</volume>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          [36]
          <string-name>
            <given-names>S.</given-names>
            <surname>Mohseni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Zarei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E. D.</given-names>
            <surname>Ragan</surname>
          </string-name>
          ,
          <article-title>A multidisciplinary survey and framework for design and evaluation of explainable ai systems</article-title>
          ,
          <source>ACM Transactions on Interactive Intelligent Systems (TiiS) 11</source>
          (
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>45</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          [37]
          <string-name>
            <given-names>M.</given-names>
            <surname>Langer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Oster</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Speith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Hermanns</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Kästner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Schmidt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sesing</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Baum</surname>
          </string-name>
          ,
          <article-title>What do we want from explainable artificial intelligence (xai)?-a stakeholder perspective on xai and a conceptual model guiding interdisciplinary xai research</article-title>
          ,
          <source>Artificial Intelligence</source>
          <volume>296</volume>
          (
          <year>2021</year>
          )
          <fpage>103473</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref38">
        <mixed-citation>
          [38]
          <string-name>
            <given-names>J.</given-names>
            <surname>Fleck</surname>
          </string-name>
          ,
          <article-title>Expertise: knowledge, power and tradeability</article-title>
          , in: Exploring expertise: Issues and perspectives, Springer,
          <year>1998</year>
          , pp.
          <fpage>143</fpage>
          -
          <lpage>171</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref39">
        <mixed-citation>
          [39]
          <string-name>
            <given-names>J.</given-names>
            <surname>Achiam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Adler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Agarwal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Ahmad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Akkaya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. L.</given-names>
            <surname>Aleman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Almeida</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Altenschmidt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Altman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Anadkat</surname>
          </string-name>
          , et al.,
          <source>Gpt-4 technical report, arXiv preprint arXiv:2303.08774</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref40">
        <mixed-citation>
          [40]
          <string-name>
            <given-names>A.</given-names>
            <surname>Aynetdinov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Akbik</surname>
          </string-name>
          ,
          <article-title>Semscore: Automated evaluation of instruction-tuned llms based on semantic textual similarity</article-title>
          ,
          <source>arXiv preprint arXiv:2401.17072</source>
          (
          <year>2024</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref41">
        <mixed-citation>
          [41]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Iter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Zhu</surname>
          </string-name>
          , G-eval:
          <article-title>Nlg evaluation using gpt-4 with better human alignment</article-title>
          ,
          <source>arXiv preprint arXiv:2303.16634</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref42">
        <mixed-citation>
          [42]
          <string-name>
            <given-names>V. B.</given-names>
            <surname>Nguyen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Schlötterer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Seifert</surname>
          </string-name>
          ,
          <article-title>From black boxes to conversations: Incorporating xai in a conversational agent</article-title>
          ,
          <source>in: World Conference on Explainable Artificial Intelligence</source>
          , Springer,
          <year>2023</year>
          , pp.
          <fpage>71</fpage>
          -
          <lpage>96</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref43">
        <mixed-citation>
          [43]
          <string-name>
            <given-names>E. M.</given-names>
            <surname>Bender</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Gebru</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>McMillan-Major</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Shmitchell</surname>
          </string-name>
          ,
          <article-title>On the dangers of stochastic parrots: Can language models be too big?</article-title>
          ,
          <source>in: Proceedings of the 2021 ACM conference on fairness, accountability, and transparency</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>610</fpage>
          -
          <lpage>623</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref44">
        <mixed-citation>
          [44]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Cui</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Cai</surname>
          </string-name>
          , L. Liu,
          <string-name>
            <given-names>T.</given-names>
            <surname>Fu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Chen</surname>
          </string-name>
          , et al.,
          <article-title>Siren's song in the ai ocean: a survey on hallucination in large language models</article-title>
          ,
          <source>arXiv preprint arXiv:2309.01219</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>