<!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>Generation be combined to Explain Query/Answer Relationships Truthfully?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Vincent Armant</string-name>
          <email>vincent.armant@ird.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Amira Mouakher</string-name>
          <email>amira.mouakher@univ-perp.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Felipe Vargas-Rojas</string-name>
          <email>felipe.vargas-rojas@ird.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Danai Symeonidou</string-name>
          <email>danai.symeonidou@inrae.fr</email>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Joris Guérin</string-name>
          <email>joris.guerin@ird.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Isabelle Mougenot</string-name>
          <email>isabelle.mougenot@umontpellier.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jean-Christophe Desconnets</string-name>
          <email>jean-christophe.desconnets@ird.fr</email>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Workshop</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Compostela, Spain</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ESPACE-DEV, IRD, Université de Montpellier, Université de Perpignan, Université Antilles, Université de Guyane, Université de la</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Mission Science Ouverte, IRD</institution>
          ,
          <addr-line>Montpellier</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Réunion</institution>
          ,
          <addr-line>Montpellier</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>UMR MISTEA, INRAE, Université de Montpellier</institution>
          ,
          <addr-line>Montpellier</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>XAI, Explanation, Resource Discovery</institution>
          ,
          <addr-line>Knowledge Graph, Retrieval-Augmented Generation, Large Language</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>In recent years, there has been a significant increase in the adoption of Large Language Models (LLMs) by users in both academic and industrial fields. These powerful tools are progressively challenging the dominance of traditional keyword-based search engines in various fields. While advancements like Retrieval-Augmented Generation (RAG) are enabling LLMs to provide provenance and explanations, their widespread adoption remains hindered by some well-known limitations, including hallucinations (factual inconsistencies), outdated knowledge, and answer precision. In contrast, classical search engines do not sufer from these issues, thanks to recent progress that has made them both eficient and accurate. However, their output may lack interpretability compared to LLMs. This vision paper proposes a novel explanation system that bridges this gap. By integrating Knowledge Graphs with RAG, we aim to elucidate the semantic relationships between retrieved resources and user queries. Addressing this research question has the potential to enhance user trust and confidence in the utilization of explainable search engines.</p>
      </abstract>
      <kwd-group>
        <kwd>Query/Answer</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Model</p>
    </sec>
    <sec id="sec-2">
      <title>1. Introduction</title>
      <p>
        In the context of high-volume, multi-source data, sophisticated solutions like Elasticsearch [
        <xref ref-type="bibr" rid="ref1 ref11 ref12 ref2">1, 2</xref>
        ] ofer
scalable and near-real-time search capabilities for eficient document retrieval. These approaches
prioritize eficiency, leveraging indexed data structures to match user queries with relevant documents.
However, less focus has been placed on explaining the semantic relationships between the retrieved
documents and the user’s intent. Conversely, entity-centric approaches that implement Applied Ontologies
and KGs [
        <xref ref-type="bibr" rid="ref13 ref14 ref3 ref4">3, 4</xref>
        ] have demonstrated efectiveness in facilitating resource discovery within heterogeneous
and multi-source data environments. Structured Knowledge Graphs which consist of resource
descriptions and their interrelationships following a data model, are well-suited for explaining the semantic
relevance between retrieved resources and the initial user request. Their straightforward knowledge
representation makes them inherently understandable to many users. However, the applicability of
KGs for explainability becomes less clear when dealing with large Knowledge Bases (KBs) containing
blank nodes, intricate relationships (transitive, complex, or nested), and alignment across diferent
KGs. In such scenarios, KGs may compromise their self-explanatory nature in favor of data integration
      </p>
      <p>CEUR</p>
      <p>
        ceur-ws.org
and interoperability. It’s important to distinguish our proposed research question from the commonly
addressed “Why” and “Why not” explanations [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ] which focus on missing results and user trust.
Our focus here is the “How” question, aiming to enhance user confidence by elucidating the semantic
connections between retrieved results and the user’s intent. This approach seeks to improve user
understanding and trust by clearly explaining how the results semantically relate to their initial queries.
      </p>
    </sec>
    <sec id="sec-3">
      <title>2. Background</title>
      <p>
        To address the dual needs of eficiency and explanations, RAG systems [
        <xref ref-type="bibr" rid="ref7 ref8 ref9">7, 8, 9</xref>
        ] have gained significant
interest in both research and industry. These systems combine the eficiency of vector-based information
retrieval with the natural language explanation capability of LLMs. RAG’s development was driven by
the need to overcome limitations inherent in LLMs, such as inaccurate answers (“hallucinations”) and
the lack of up-to-date, domain-specific, or private information.
      </p>
      <p>
        Figure 1 illustrates the general architecture of RAG systems [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. A user initiates the process by
submitting a query. The retriever then searches various data sources, including local or external
databases, private documents, web applications, or APIs. The LLM then creates a context by merging
the retrieved information with the initial user query. This context serves as a one-shot learning
experience for the LLM, enabling it to leverage this additional knowledge to potentially generate more
accurate answers for the specific query. The accuracy of the constructed context directly influences the
quality of the answers returned by the LLM, as well as the likelihood of hallucinations. We propose a
novel system architecture that explains the semantic relationships between user queries and retrieved
resources, building upon this framework.
      </p>
    </sec>
    <sec id="sec-4">
      <title>3. Prospective System Architecture</title>
      <p>This work envisions a prospective workflow that utilizes RAG. In the sequel, we present the system
architecture, which aims to automatically construct user-centric explanations that connect a user
query to the retrieved resources. We then discuss the implementation challenges of the prospective
architecture. Figure 2 shows the prospective system architecture intended to explain to users how their
queries semantically relate to the retrieved resources. At the beginning of the pipeline, the user inputs
a search term (basic user query) and a profile.</p>
      <p>The system aims to provide both textual and graphical explanations that describe the relationship
between the user’s query and the retrieved resources.</p>
      <p>1. The Semantic Relationship Retrieval component follows a well-established Semantic Web Search
workflow. This workflow involves enriching the user query with related concepts before
evaluating it against a structured knowledge base. However, unlike the classical approach, which
solely focuses on retrieving relevant resources, this component identifies a set of paths. Each
path represents a sequence of semantic relationships connecting the user’s search term to the
retrieved resources. The combined set of these paths forms a knowledge graph, integrating
relevant knowledge extracted from both the knowledge base and external resources.
2. The Knowledge Shape Selection component takes the user profile (i.e., general user, domain
expert) as input and outputs a knowledge shape. This knowledge shape represents the set of
sentences that the user profile is likely to understand. We use the knowledge shape to format
both the semantic relationships from the Knowledge Composition component and the output
from the verified LLM.
3. The User-Centric Knowledge Composition component utilizes the user’s knowledge shape to
transform the retrieved semantic paths into a knowledge graph that is comprehensible to the
user. This resulting knowledge graph is then verbalized using appropriate techniques, creating
the context for the LLM.
4. The Verified LLM component receives three inputs: the verbalized, user-understandable
knowledge graph as context, and the question “How does the user query relate to the retrieved
resources?” as the query. It provides explanations to the user in both textual and graphical formats.
This component goes beyond the traditional RAG pipeline by incorporating an answer verification
setup. This verification process ensures that the returned graph is consistent with the previously
determined knowledge shape.
5. At the end of the pipeline, we expect a significant decrease in the occurrence of hallucinations
within the explanations. This prioritizes verifiability and user comprehension, potentially leading
to fewer expression explanations. This trade-of captures the natural conflict in LLM answers
between expressiveness and consistency.</p>
    </sec>
    <sec id="sec-5">
      <title>4. Some Challenges</title>
      <p>Semantic Relationship Retrieval: Unlike the traditional semantic web workflow, which only returns
retrieved resources, the Semantic Relationship Retrieval component requires additional computational
efort. This challenge involves designing fast, federated approaches capable of querying external
endpoints and composing semantic paths eficiently to enable real-time user interactions.
Knowledge Shape Selection: Choosing an appropriate language to model knowledge that is
comprehensible to diverse user profiles presents a key challenge. For instance, the SHACL language ofers an
expressive framework for modeling authorized knowledge using SHACL shapes. In this context, a user
profile’s knowledge shape might represent complex constraints restricting vocabulary usage or limiting
nested knowledge representation.</p>
      <p>The User-Centric Knowledge Composition: Rewriting the retrieved semantic path, extracted from
an open knowledge repository and conforming to a knowledge shape, presents a significant challenge.
The success of this process depends on the diference between the complexity of the retrieved semantic
path (the presence of nested structures and blank nodes) and the simplicity of the user-understandable
knowledge shape.</p>
      <p>The Verified LLM : Given a context and a query, recent advances in LLMs and RAG technologies (e.g.,
ChatGPT 4.0) already enable contextual text and graph-based explanations. This last feature partially
mitigates the recurring criticism by minimizing the occurrence of hallucinations. In this direction, our
prospective pipeline not only envisions feeding these tools with structured and connected knowledge
contexts, but it also envisions verifying that the outcome will be both consistent and understandable by
the user. With this last challenge, we hope to drastically reduce the number of hallucinations.
Evaluation and Comparison of Approaches: A significant challenge lies in comparing explanation
generation approaches, given the subjective nature of interpretability. Evaluating the efectiveness of
proposed systems without relying on large cohorts of human participants to assess responses is not
straightforward. This subjectivity makes it dificult to establish objective metrics for measuring the
quality and usefulness of explanations. To properly assess the KG + RAG approach, an experimental
protocol should involve both an evaluation of the semantic accuracy and relevance of explanations by
domain experts and a user study with participants from various backgrounds to gauge comprehension
and perceived usefulness of the explanations.</p>
    </sec>
    <sec id="sec-6">
      <title>5. Conclusion</title>
      <p>This vision paper addresses the challenge of explaining the semantic relationship between user queries
and retrieved resources in search engine results. First, we introduce the strengths and limitations of
traditional keyword-based search engines. Next, we delve into the latest explanation capabilities of RAG.
This comprehensive framework addresses common problems with LLMs like hallucinations, outdated
knowledge, and a deficiency in domain-specific expertise. To address the challenges of truthfully
and accurately explaining to users how their queries relate to the retrieved resources, we present a
prospective system that leverages Semantic Web and knowledge graphs. This system aims to improve
the context provided by the RAG system and verify the accuracy of its explanations.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>This study was made possible thanks to discussions initiated during the kick-of meeting of the MOSAIC
Horizon Europe project (grant number: 101137398).</p>
    </sec>
    <sec id="sec-8">
      <title>A. Appendix</title>
      <p>In this appendix, we provide an illustrative example utilizing ChatGPT-4. The sections with a grey
background represent the prompts we used, while the sections with a white background display the
responses generated by ChatGPT-4.</p>
      <p>A.1. Explaining Ocean Data Properties</p>
      <p>The dataset D1 has the title “Observations of the Pacific Ocean”. The Observation
Collection O1 has aggregated results the dataset D1. O1 has members Observation Collections
O3 and O4. O3 has the Observed Property “Water Conductivity”, and O4 has the Observed
Property “Temperature at 5-meter depth”. “Water Conductivity” and “Temperature at
5-meter depth” are both Observed properties of the Sea. Water Conductivity can only
be understood by experts while ”Temperature at 5-meter depth” can be understood by
non-experts. Can you explain to non-experts how D1 relates to Sea-observed properties?
To explain the relationship between the dataset D1 and the observed properties of the
sea in a way that non-experts can understand, let’s break it down:
1. Dataset D1: ”Observations of the Pacific Ocean” - This is a collection of data
gathered about various aspects of the Pacific Ocean. Think of it like a big book
that records diferent measurements and observations made in the ocean.
2. Observation Collection O1 - This is like a chapter in the book (D1) that focuses
on specific aggregated results. It’s a grouping of related data.
3. Observation Collections O3 and O4 - These are sub-chapters under O1. They
focus on specific topics or types of measurements:
• O3 deals with ”Water Conductivity.” This is a measure of how well the water
conducts electricity, which can tell experts a lot about the water’s salt content
and overall quality.
• O4 focuses on ”Temperature at 5-meter depth,” which is simply measuring</p>
      <p>how warm or cool the water is at a depth of 5 meters below the surface.
4. Observed Properties of the Sea - These are the specific characteristics of the
sea that are being measured. In this case, the key observed properties are:
• Water Conductivity: Important for understanding the salt content and
other chemical properties of seawater. This might be more technical and
usually understood by experts in oceanography.
• Temperature at 5-meter depth: This is a straightforward measurement
of how warm the water is at a certain depth. It’s similar to measuring air
temperature and can be easily understood by anyone.</p>
      <p>Simplified Explanation for Non-Experts
Imagine Dataset D1 as a comprehensive report on the Pacific Ocean, detailing
various characteristics of the sea. Observation Collection O1 is a specific section
of this report that pulls together data on particular topics. Within O1, there are
two important parts:
1. One part (O3) looks at how salty or conductive the water is, which is more
technical and mainly useful for scientists.
2. The other part (O4) simply checks the water temperature at a certain depth,
which is more straightforward and can be understood by anyone.</p>
      <p>These measurements help scientists understand the state of the ocean, such as
how it changes over time and what might be causing those changes.</p>
      <p>Can you draw the graph of the context?
Here’s the contextual graph illustrating the relationship between the dataset D1, the
observation collections, and the observed properties of the sea:</p>
      <p>The arrows indicate the hierarchical structure and how each part contributes to
understanding the properties of the sea.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>C.</given-names>
            <surname>Gormley</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Tong</surname>
          </string-name>
          ,
          <article-title>Elasticsearch: the definitive guide: a distributed real-time search and analytics engine, ”</article-title>
          <string-name>
            <surname>O'Reilly Media</surname>
          </string-name>
          , Inc.”,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>N.</given-names>
            <surname>Kathare</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O. V.</given-names>
            <surname>Reddy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Prabhu</surname>
          </string-name>
          ,
          <article-title>A comprehensive study of elasticsearch</article-title>
          ,
          <source>International Journal of Science and Research (IJSR)</source>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A.</given-names>
            <surname>Chapman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Simperl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Koesten</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Konstantinidis</surname>
          </string-name>
          , L.
          <string-name>
            <surname>-D. Ibáñez</surname>
            , E. Kacprzak,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Groth</surname>
          </string-name>
          ,
          <article-title>Dataset search: a survey</article-title>
          ,
          <source>The VLDB Journal</source>
          <volume>29</volume>
          (
          <year>2020</year>
          )
          <fpage>251</fpage>
          -
          <lpage>272</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>K.</given-names>
            <surname>Balog</surname>
          </string-name>
          , Entity-oriented search, Springer Nature,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>A.</given-names>
            <surname>Chapman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Jagadish</surname>
          </string-name>
          , Why not?,
          <source>in: Proceedings of the 2009 ACM SIGMOD International Conference on Management of data</source>
          ,
          <year>2009</year>
          , pp.
          <fpage>523</fpage>
          -
          <lpage>534</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>N.</given-names>
            <surname>Bidoit</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Herschel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Tzompanaki</surname>
          </string-name>
          ,
          <article-title>Query-based why-not provenance with nedexplain</article-title>
          ,
          <source>in: Proceedings of the 17th International Conference on Extending Database Technology, EDBT</source>
          <year>2014</year>
          , Athens, Greece, March
          <volume>24</volume>
          -28,
          <year>2014</year>
          ,
          <year>2014</year>
          , pp.
          <fpage>145</fpage>
          -
          <lpage>156</lpage>
          .
          <source>doi:1 0 . 5 4</source>
          <volume>4 1</volume>
          / 0 0 2 / E D B T .
          <volume>2 0 1 4 . 1</volume>
          <fpage>4</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>P.</given-names>
            <surname>Lewis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Perez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Piktus</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Petroni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Karpukhin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Goyal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Küttler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lewis</surname>
          </string-name>
          , W.-t. Yih,
          <string-name>
            <given-names>T.</given-names>
            <surname>Rocktäschel</surname>
          </string-name>
          , et al.,
          <article-title>Retrieval-augmented generation for knowledge-intensive nlp tasks</article-title>
          ,
          <source>Advances in Neural Information Processing Systems</source>
          <volume>33</volume>
          (
          <year>2020</year>
          )
          <fpage>9459</fpage>
          -
          <lpage>9474</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Mao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>He</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Shen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Gao</surname>
          </string-name>
          , J. Han,
          <string-name>
            <surname>W</surname>
          </string-name>
          . Chen,
          <article-title>Generation-augmented retrieval for open-domain question answering</article-title>
          , arXiv preprint arXiv:
          <year>2009</year>
          .
          <volume>08553</volume>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>G.</given-names>
            <surname>Izacard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Lewis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lomeli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Hosseini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Petroni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Schick</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Dwivedi-Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Joulin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Riedel</surname>
          </string-name>
          , E. Grave, Atlas:
          <article-title>Few-shot learning with retrieval augmented language models</article-title>
          ,
          <source>Journal of Machine Learning Research</source>
          <volume>24</volume>
          (
          <year>2023</year>
          )
          <fpage>1</fpage>
          -
          <lpage>43</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>A.</given-names>
            <surname>Kimothi</surname>
          </string-name>
          ,
          <string-name>
            <surname>Retrieval Augmented Generation - A Simple Introduction</surname>
          </string-name>
          ,
          <year>2024</year>
          . URL: https:// abhinavkimothi.gumroad.com/l/RAG.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          1. D1:
          <article-title>Observations of the Pacific Ocean - The main dataset containing comprehensive observations</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          2. O1:
          <article-title>Aggregated Results - A collection of specific results derived from D1</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          3. O3:
          <article-title>Water Conductivity and O4: Temperature at 5-meter depth - Specific observation collections under O1, focusing on diferent aspects of the sea</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Observed</given-names>
            <surname>Properties</surname>
          </string-name>
          :
          <article-title>Sea - The overarching category for properties like water conductivity and temperature, indicating the specific aspects of the ocean being measured</article-title>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>