<!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>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Here's Charlie! Realising the Semantic Web vision of Agents in the age of LLMs</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Wright</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jesse</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Computer Science Department, University of Oxford</institution>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>RDF Surfaces</institution>
          ,
          <addr-line>Semantic Web, Proof, Proof Engine, Solid</addr-line>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2024</year>
      </pub-date>
      <fpage>13</fpage>
      <lpage>15</lpage>
      <abstract>
        <p>This paper presents our research towards a near-term future in which legal entities, such as individuals and organisations can entrust semi-autonomous AI-driven agents to carry out online interactions on their behalf. The author's research concerns the development of semi-autonomous Web agents, which consult users if and only if the system does not have suficient context or confidence to proceed working autonomously. This creates a user-agent dialogue that allows the user to teach the agent about the information sources they trust, their data-sharing preferences, and their decision-making preferences. Ultimately, this enables the user to maximise control over their data and decisions while retaining the convenience of using agents, including those driven by LLMs.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>CEUR
ceur-ws.org</p>
    </sec>
    <sec id="sec-2">
      <title>1. Introduction</title>
      <p>
        There exists a substantial body of research on communication protocols for multi-agent systems,
and it is reflected in the vision of the Semantic Web itself [
        <xref ref-type="bibr" rid="ref1 ref2 ref3">1, 2, 3</xref>
        ] as shown by Charlie, the “AI that
works for you”. Yet, the 2006 lamentation that “[b]ecause we haven’t yet delivered large-scale,
agent-based mediation, some commentators argue that the Semantic Web has failed” [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] still
rings true today. The growing use of LLMs raises a key challenge in building Trustworthy and
Reliable Web Agents [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ]. This is heightened by growing interest among LLM researchers in
building dialogues between multiple LLMs [
        <xref ref-type="bibr" rid="ref7 ref8">7, 8</xref>
        ]. Moreover, recent research indicates the strong
potential of the Semantic Web to complement emerging LLM technologies [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. For example,
the use of Retrieval Augmented Generation (RAG) with Knowledge Graphs has shown to be
efective in grounding LLM queries [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. The universal semantics and proof mechanisms of the
Semantic Web stack are therefore pertinent to the successful development of semi-autonomous
Web agents using LLMs.
https://www.cs.ox.ac.uk/people/jesse.wright/ (W. Jesse)
      </p>
      <p>© 2024 Copyright for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).</p>
    </sec>
    <sec id="sec-3">
      <title>2. Design Requirements</title>
      <p>
        We identify the following non-functional requirements for an agent communication protocol.
It must be possible for semi-autonomous agents to:
1. Identify legal entities, such as individuals or organisations, on the Web [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] so they can
be referenced.
2. Deterministically discover other agents representing an entity from their Web identity [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>
        This does not require all agents to be publicly advertised; some may be discovered from
links to protected documents.
3. Describe, and agree to, any usage controls [
        <xref ref-type="bibr" rid="ref12 ref13 ref14">12, 13, 14</xref>
        ] associated with data they exchange.
      </p>
      <p>
        This allows sharing of protected data while articulating the recipient’s legal or moral
obligations [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
4. Describe the origin and provenance of data they exchange. In an open world of agents
that can “say anything about anything,” systems can identify which external claims to
believe for a given task, based on the agent’s internal trust model.
5. Unambiguously describe ground truths they send, and agreements they make, using a
formal representation. Consider the case where an individual’s agent purchases a flight
from an airline’s agent. Structured ground truths eliminate an LLM’s risk of hallucination
or misinterpretation of key information, such as the flight time (“10 o’clock” could be 22:00
or 10:00). As agents represent entities in binding agreements, this approach also reduces
the risk of legal disputes by limiting the subjectivity of agreed terms and thus the ability to
reinterpret or rescind them [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. Furthermore, agents can implement rule-based internal
safeguards, such as user-defined daily spending limits. Truly generic agents may generate
and communicate structured ontologies when encountering new tasks. In many cases
we expect LLM-supported ontology construction [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] to facilitate generation; however,
research is required to understand how (1) agents can align on conceptual models for use
and (2) how human oversight can be maintained without disrupting user experience.
6. Contextualise a task which may be ambiguous or poorly defined, such that interacting
agents can introduce new solution spaces or negotiating actors in a serendipitous manner.
      </p>
    </sec>
    <sec id="sec-4">
      <title>3. Sample Use-Case and Implementation</title>
      <p>We implemented the following flow where agents act as personal assistants
for individual users:
1. Jun types into a chat “Schedule a meeting with Nigel next week”;
2. Jun’s agent identifies data to be shared with Nigel and requests relevant
sharing permissions from Jun (where not already obtained);
3. Nigel’s agent receives a request from Jun;
4. Nigel is prompted to confirm that he believes Jun is an authoritative source
of truth for her calendar (where not already obtained);
5. Nigels agent proposes a meeting time to Nigel; and
6. the meeting is proposed to Jun’s agent and automatically confirmed.</p>
      <p>
        We have created a running demo with a video, flow-diagrams (including Figure 1) and other
resources for our codebase1. The implementation corresponds to the above use-case steps:
1. Given the user prompt and a set of known WebID profiles [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], an LLM called by Jun’s
agent identifies the relevant entities for the agent to negotiate with (Nigel), and the
WebIDs of those entities. Given the user prompt, and the user’s personal knowledge
graph, an LLM called by Jun’s agent identifies which subset (as a list of named graphs) of
the user data are needed to fulfil the user’s request.
2. Notation3 [18] reasoning is used to identify the policies applicable to the data subset. In
the available demo recording, policies are encoded in ACP [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]; we are currently migrating
to use ODRL [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] and DPV [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. If these policies do not yet permit read access to Nigel,
Jun is prompted to modify them. Jun’s agent then dereferences Nigel’s WebID [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] to
discover information about his agent.
3. Jun’s agent uses an LLM to construct a message for Nigel’s agent, explaining the context
of Jun’s task: “Jun seeks to schedule a meeting for next week. Propose a time for Jun and
Nigel to meet using their calendars.” Jun’s agent sends Nigel’s agent this message along
with the RDF description of Jun’s calendar and any associated policies and provenance.
With ACL, Nigel’s agent does not need to agree to any policy obligations; this changes
with ODRL. The provenance in this case is simply a signature of the canonicalised calendar
dataset [19] using Jun’s public key.
1https://github.com/jeswr/phd-language-dialogue-experiment
4. As Nigel has instructed his agent that Jun is an authoritative source of information on
all topics, his agent believes (takes as ground truth) the signed RDF dataset sent by her
agent. We are developing conceptual models for agentic trust; these extend existing trust
vocabularies [20, 21, 22, 23] with a range of features including (1) qualifying whether
sources are trusted for particular types of claims; for instance, most agents should trust
certified airlines to present flight times and prices, but not medical data (2) qualifying
the forms of provenance secure enough for a given task; for instance, an insurance
provider may require provenance demonstrating a user was signed in with two-factor
authentication when entering financial details to their knowledge base.
5. Nigel’s agent proposes a meeting time, using the natural language context (not a ground
truth) and the calendar dataset (ground truth). The LLM proposes a meeting time, then
the N3 reasoner applies rules to (1) ensure no calendar conflicts and (2) check for user
confirmation, before adding the proposed time to the knowledge base. In a future iteration,
we plan to use the LLM to generate an N3 query that proposes a meeting time based on
Nigel’s Personal Data Store and Jun’s calendar.
6. Upon meeting the above requirements, the reasoner sends to Jun’s agent a meeting
proposal, in the form of an RDF dataset with attached usage policies and provenance.
Jun’s agent confirms this dataset can be believed based on the internal trust model. The
rules within Jun’s agent validate that there are no conflicting events. Jun’s personal
knowledge base is updated with the event, and a confirmation is sent to Nigel’s agent.
      </p>
    </sec>
    <sec id="sec-5">
      <title>4. Conclusion and Future Research</title>
      <p>We have implemented a generic personal assistant that communicates using a protocol satisfying
the requirements of Section 2. Future work will make the design requirements more rigorous
by (1) gathering requirements for personal agents through user studies, and (2) engaging with
industry to develop specialised agents, including product sales agents. Concurrently, we shall
formalise the vocabularies for exchanging provenance and terms of use between agents and
modelling trust and data policies within agents, extending those vocabularies discussed in
Section 3. Once these vocabularies mature, we will develop reasoning specifications to mediate
between the internal representations and exchanged metadata. This enables agents to negotiate
to obtain suficient provenance to believe claims, and find agreeable data terms of use between
agents - whilst concurrently updating their internal models via user interaction.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgements</title>
      <p>Jesse Wright is funded by the Department of Computer Science, University of Oxford.
supported approach to ontology and knowledge graph construction, 2024. URL: https:
//arxiv.org/abs/2403.08345. arXiv:2403.08345.
[18] T. Berners-Lee, Notation3, http://www.w3.org/DesignIssues/Notation3.html (1998).
[19] D. Longley, G. Kellogg, D. Yamamoto, M. Sporny, Access Control Policy (ACP), Solid</p>
      <p>Editor’s Draft, W3C, 2022. https://w3c.github.io/WebID/spec/identity/.
[20] M. Richardson, R. Agrawal, P. Domingos, Trust management for the semantic web, in:</p>
      <p>International semantic Web conference, Springer, 2003, pp. 351–368.
[21] S. Galizia, Wsto: A classification-based ontology for managing trust in semantic web
services, in: European semantic web conference, Springer, 2006, pp. 697–711.
[22] W. Sherchan, S. Nepal, J. Hunklinger, A. Bouguettaya, A trust ontology for semantic
services, in: 2010 IEEE International Conference on Services Computing, IEEE, 2010, pp.
313–320.
[23] G. Amaral, T. P. Sales, G. Guizzardi, D. Porello, Towards a reference ontology of trust,
in: On the Move to Meaningful Internet Systems: OTM 2019 Conferences: Confederated
International Conferences: CoopIS, ODBASE, C&amp;TC 2019, Rhodes, Greece, October 21–25,
2019, Proceedings, Springer, 2019, pp. 3–21.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>O.</given-names>
            <surname>Lassila</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Hendler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Berners-Lee</surname>
          </string-name>
          ,
          <article-title>The semantic web</article-title>
          ,
          <source>Scientific American</source>
          <volume>284</volume>
          (
          <year>2001</year>
          )
          <fpage>34</fpage>
          -
          <lpage>43</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>S.</given-names>
            <surname>Luke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Spector</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Rager</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Hendler</surname>
          </string-name>
          ,
          <article-title>Ontology-based web agents</article-title>
          ,
          <source>in: Proceedings of the first international conference on Autonomous agents</source>
          ,
          <year>1997</year>
          , pp.
          <fpage>59</fpage>
          -
          <lpage>66</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>S.</given-names>
            <surname>Poslad</surname>
          </string-name>
          ,
          <article-title>Specifying protocols for multi-agent systems interaction</article-title>
          ,
          <source>ACM Transactions on Autonomous and Adaptive Systems (TAAS) 2</source>
          (
          <year>2007</year>
          )
          <fpage>15</fpage>
          -
          <lpage>es</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>N.</given-names>
            <surname>Shadbolt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Berners-Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Hall</surname>
          </string-name>
          ,
          <article-title>The semantic web revisited</article-title>
          ,
          <source>IEEE Intelligent Systems</source>
          <volume>21</volume>
          (
          <year>2006</year>
          )
          <fpage>96</fpage>
          -
          <lpage>101</lpage>
          . doi:
          <volume>10</volume>
          .1109/MIS.
          <year>2006</year>
          .
          <volume>62</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Deng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Lin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-R.</given-names>
            <surname>Wen</surname>
          </string-name>
          , T.-S. Chua,
          <article-title>Large language model powered agents in the web, learning 2 (</article-title>
          <year>2024</year>
          )
          <fpage>20</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>L.</given-names>
            <surname>Sun</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Lyu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Li</surname>
          </string-name>
          , et al.,
          <article-title>Trustllm: Trustworthiness in large language models</article-title>
          ,
          <source>arXiv preprint arXiv:2401.05561</source>
          (
          <year>2024</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Q.</given-names>
            <surname>Wu</surname>
          </string-name>
          , G. Bansal,
          <string-name>
            <given-names>J.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , E. Zhu,
          <string-name>
            <given-names>B.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Jiang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Wang</surname>
          </string-name>
          , Autogen:
          <article-title>Enabling next-gen llm applications via multi-agent conversation framework</article-title>
          ,
          <source>arXiv preprint arXiv:2308.08155</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Deng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , W. Lam, S.
          <article-title>-</article-title>
          K. Ng, T.-S. Chua,
          <string-name>
            <surname>Plug-</surname>
          </string-name>
          and
          <article-title>-play policy planner for large language model powered dialogue agents</article-title>
          ,
          <source>in: The Twelfth International Conference on Learning Representations</source>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>J.</given-names>
            <surname>Wright</surname>
          </string-name>
          ,
          <article-title>The old and the new - using semantic web technologies to build better</article-title>
          <source>AI</source>
          ,
          <year>2024</year>
          . URL: https://blog.jeswr.org/
          <year>2024</year>
          /04/18/better-ai.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Kang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Kwak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Baek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. J.</given-names>
            <surname>Hwang</surname>
          </string-name>
          ,
          <article-title>Knowledge graph-augmented language models for knowledge-grounded dialogue generation</article-title>
          ,
          <source>arXiv preprint arXiv:2305.18846</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>H.</given-names>
            <surname>Story</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Berners-Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sambra</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Taelman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Scazzosi</surname>
          </string-name>
          ,
          <source>Web Identity (WebID) 1.0, W3C Community Group Final Report, W3C</source>
          ,
          <year>2024</year>
          . https://w3c.github.io/WebID/spec/identity/.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>M.</given-names>
            <surname>Bosquet</surname>
          </string-name>
          ,
          <source>Access Control Policy (ACP)</source>
          ,
          <source>Solid Editor's Draft, W3C</source>
          ,
          <year>2022</year>
          . https://w3c. github.io/WebID/spec/identity/.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>R.</given-names>
            <surname>Iannella</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Villata</surname>
          </string-name>
          ,
          <source>Odrl information model 2</source>
          .2,
          <year>2023</year>
          . URL: https://www.w3.org/TR/ 2018/REC-odrl-model-
          <volume>20180215</volume>
          /.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>H. J.</given-names>
            <surname>Pandit</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Polleres</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Bos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Brennan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Bruegger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. J.</given-names>
            <surname>Ekaputra</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. D.</given-names>
            <surname>Fernández</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. G.</given-names>
            <surname>Hamed</surname>
          </string-name>
          , E. Kiesling,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lizar</surname>
          </string-name>
          , et al.,
          <article-title>Creating a vocabulary for data privacy: The ifrst-year report of data privacy vocabularies and controls community group (dpvcg), in: On the Move to Meaningful Internet Systems: OTM 2019 Conferences: Confederated International Conferences: CoopIS</article-title>
          , ODBASE,
          <string-name>
            <surname>C</surname>
          </string-name>
          &amp;
          <article-title>TC 2019, Rhodes</article-title>
          , Greece,
          <source>October 21-25</source>
          ,
          <year>2019</year>
          , Proceedings, Springer,
          <year>2019</year>
          , pp.
          <fpage>714</fpage>
          -
          <lpage>730</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>J.</given-names>
            <surname>Wright</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Esteves</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <article-title>Me want cookie! towards automated and transparent data governance on the web</article-title>
          ,
          <year>2024</year>
          . URL: https://arxiv.org/abs/2408.09071. arXiv:
          <volume>2408</volume>
          .
          <fpage>09071</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>M.</given-names>
            <surname>Garcia</surname>
          </string-name>
          , What Air Canada Lost In 'Remarkable'
          <article-title>Lying AI Chatbot Case</article-title>
          , https://www.forbes.com/sites/marisagarcia/2024/02/19/ what-air
          <article-title>-canada-lost-in-remarkable-lying-ai-chatbot-</article-title>
          <string-name>
            <surname>case</surname>
            <given-names>/</given-names>
          </string-name>
          ,
          <year>2024</year>
          . [Accessed 05-
          <fpage>07</fpage>
          - 2024].
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>V. K.</given-names>
            <surname>Kommineni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>König-Ries</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Samuel</surname>
          </string-name>
          ,
          <article-title>From human experts to machines: An llm</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>