<!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 />
    <article-meta>
      <title-group>
        <article-title>Enhanced LLM for smart Knowledge Management in nuclear industry</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Frédéric Godest</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mouna El Alaoui</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Victor Richet</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Robert Plana</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lies Benmiloud-Bechet</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jean-François Bossu</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Olivier Malhomme</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Assystem Engineering and Operation Services</institution>
          ,
          <addr-line>9/11 Allée de l'Arche, 92610 Courbevoie</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The nuclear industry, characterized by its large-scale projects and intricate processes, requires robust knowledge management (KM) strategies. Traditional KM approaches, such as training, documentation, and expert networks, have been employed to address this need . Documentation, though, has challenged by its volume, the outcome of this approach. However, the advent of AI and Large Language Models (LLMs) has opened new avenues for KM innovation. This paper explores the integration of CurieLM, a domain-specific LLM, with a nuclear ontology to improve the quality of knowledge retrieval and answers generation. By automatically expanding the input context through ontology-driven enrichment, our approach aims to address the shortcomings of existing KM methods, offering a scalable and efficient solution for the nuclear industry's unique challenges.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Large Language Model</kwd>
        <kwd>Ontology</kwd>
        <kwd>Knowledge Management</kwd>
        <kwd>Nuclear Industry 1</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Nuclear power plants are highly knowledge-intensive facilities [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] structured by long-term projects
involving multiple disciplines and complex technologies. Alongside this growing complexity, the
nuclear domain is facing actual challenges of growing decarbonization demand and replacement of
the aging nuclear fleets [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The lifespan of power plants also stresses the importance of integration
of heterogenous knowledge means, which can go back to 50 years. In order to meet the resulting
high expectations and requirements of this critical domain, capturing and capitalizing on knowledge
plays a crucial role. In fact, Knowledge Management (KM) has been identified as one of the key
enabling discipline for distributed engineering enterprises such as nuclear power plant projects in
the 21st century [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>
        Knowledge Management is defined by [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] as the practice of selectively applying knowledge from
previous experiences of decision making to current and future decision-making. To successfully
achieve this knowledge capitalization and application in the future decisions, it is essential to
consider the capture, storage, retrieval, and reuse of knowledge [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. One of the main KM’s objectives
is providing appropriate information for the appropriate resource at the right time [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ][
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] which
makes it essential in the context of the nuclear project.
      </p>
      <p>
        Recent advancements in data-related digital technologies, particularly Artificial Intelligence (AI)
led to the development of Large Language Models (LLMs). Training LLMs on numerous, diverse texts
results in the integration of extensive knowledge, interpretation of complex information, general
reasoning and aiding knowledge-intensive decision-making [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. The recent evolution of LLMs have
enabled the creation of Generative AI, a technology can understand and generate human-like text.
Few experiments have been made in the nuclear domain, NukeBERT [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] is a pre-trained language
model based on BERT [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] that has exhibited significant performance improvements over the original
BERT. Another is NuclearQA [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] that introduced a human-made benchmark aimed at assessing
language models in the nuclear domain.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. LLM limitations in Knowledge Management</title>
      <p>
        Despite their undeniable benefits, the responses generated by LLMs present two main limitations: (i)
outdated information potentially originating from the model's training date, and (ii) inaccuracies in
factual representation, also known as “hallucinations” [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. LLM ‘hallucinations’ designates the LLM’s
generation of incorrect results and answers. It is either due to the fact that the requested information
has not been retrieved, or the fact that LLM tries to provide a creative answer.
      </p>
      <p>Additionally, hardware is also an important limitation regarding LLM, especially in the nuclear
industry where, most of the time, a local LLM is required so that the confidentiality and the security
of the sensitive information is guaranteed. This constraint induces purchasing and installing
Graphics Processing Unit (GPU) to specific servers. These GPU are rather expensive due to their use
of more electrical resources than a regular computer. It also echoes on the IT infrastructure, such as
installing GOPUs.</p>
      <p>These limitations must be addressed to achieve a KM tool with a reliable and energy-efficient
LLM developed for use in the nuclear industry.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Addressing LLMs limitations</title>
      <p>This work aims to mitigate the previously described limitations through the following approaches.</p>
      <p>LLM generated answers quality:
1. Larger LLM could prevent LLM hallucinations since it has much more trained parameters
and could also better “understand” the questions and the overall context.
Larger LLM also need more computer power to operate and, sometimes, the necessary power
can only be provided by third party companies (ex: OpenAI, Microsoft, AWS, etc.).
2. Retrieval-Augmented Generation (RAG) architecture is expected to provide precise context
to the LLM when the documentary corpus quality is adequate. RAG architecture can work
with “small” LLM (7b to 14b parameters) and can provide an equivalent quality of generated
answer as larger LLM.
3. Fine tuning a LLM enables improvement of the generated answers in a specific domain. In
this case, training instructions related to nuclear domain has been provided to a LLM for its
fine tuning.
4. Increasing the context sent to the LLM; The more the LLM has context, the better. This
context can be increased by prompt engineering</p>
      <p>This last aspect is the one addressed in our proposal. The idea is to use ontology-enriched request,
or in other words, on the basis of an ‘elementary’ request, expand it using ontology. This means on
the basis of the concepts used in the request, use the closest concepts in the ontology as concept to
further enhance quality of the answers. This approach has not been implemented for the generation
of the results below.</p>
      <p>LLM energy efficiency:
1. The best way to reduce the energy consumption is to get a “tiny” LLM (&lt;7b parameters). But
this solution also comes with a downside; Smaller LLM are in fact less “intelligent” and will,
by definition, provide poorer quality responses.
2. A common way to reduce energy consumption without drastically degrading the quality of
the generated answer is to get a “small” LLM (7b to 14b parameters) and to quantize it. LLM
quantization is a way of compressing LLM by changing the variables type of the parameters
(ex: from float to int8) so it will need less memory to operate</p>
      <p>Those two approaches were successfully implemented in the previous version of CurieLM,
enabling significant increase of the performance, most noticeably the time to generate an answer.
3. Lastly, LLM are commonly used within Python projects. Some of the LLM have been
redesigned so they can work on C++ program which is way more efficient. The major
downside of this method is the integration within existing tools and larger projects since,
nowadays, the community is mainly working on Python.</p>
      <p>These solutions highlight the fact that there is a trade-off between computer power and generated
answers quality but some of the technical levers might be used to optimize this trade off to our need
of efficiency.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Methodology</title>
      <p>Our first approach consists in combining a fine-tuned “small” LLM (7b parameters) which is then
quantized within a RAG architecture implemented in a Knowledge Management solution. We called
this project CurieLM (which stands for Marie Curie ). This model has been fine-tuned over 25 000
instructions from internal dataset and open-source dataset related to nuclear domain.</p>
      <p>Models have been compared on 5 main characteristics, which have been human-evaluated by a
pool of experts. Those characteristics are described below:
•
•
•
•
•</p>
      <p>Accuracy: Capability of the model to provide an accurate answer, without using vague words,
or concepts
Synthesis: Capability of the model to provide a short answer, expressed as much as possible
in the shortest way possible
Quality: Capability of the model to provide an answer using the relevant elements, up to date
Exhaustivity: Capability of the model to answer to the whole question, without shadowing
or omitting some aspects of the question
Clarity: Capability of the model to provide structured and organised answer, easy to read and
understand</p>
    </sec>
    <sec id="sec-5">
      <title>5. Results</title>
      <p>We tested GPT4 and our CurieLM RAG architecture through 56 technical questions related to nuclear
safety. After human evaluation, we observed a significant augmentation of the quality of the answer
(higher notes), and a constant consistency (lower standard deviation) with the RAG technology. This
evaluation was specifically performed on the exhaustivity, accuracy, overall quality, clarity and
synthesis of the answer (Figure 1) which were expert-evaluated.</p>
      <p>We also tested our fine-tuned CurieLM (with more than 23 000 instructions) model with a custom
benchmark dataset related to nuclear domain to compare with Mistral 7b (our base model) and other
models like GPT4. (Figure 2). This comparison will be evaluated thanks to evaluation dataset
composed of questions and answers related to nuclear domain. Due to data safety and confidentiality
constraints, this datasets cannot be disclosed in details but are described in [10]. Those datasets have
been built under the form of Q/A sets defined by internal experts group.
2,00
1,00
0,00
0,88
0,14
0,77 0,86</p>
      <p>Explanation for the KPI used in this chart is provided in paragraph 4. For each question of the
dataset considered, every generated answer will be then compared to the correct answer in the
dataset. The ratio between the correct and incorrect generated answer will give us the accuracy of
the model in Figure 2.</p>
      <p>Model Accuracies</p>
      <p>17%
16%</p>
      <p>20%</p>
      <p>Accuracy [%]
0%
5%
10%
15%
25%
30%
35%
40%</p>
      <p>We can observe that GPT4 provided correct answers only with 35% of accuracy even though
GPT4 is one of the largest LLM available on the market. We can also observe that Mistral 7b (our
base model) provided correct answers with 16% of accuracy and, when fine-tuned, this accuracy is
slightly better with only 17% of accuracy.</p>
      <p>These results highlight the fact that for very specific domains, LLMs have not great accuracy in
terms of answers quality. We can draw another graphic if we define LLM efficiency as such:
!""#$#!%$&amp; =</p>
      <p>'$$()'$&amp;
%*_,')'-!.!)/</p>
      <p>Model Efficiencies
GPT4-Turbo</p>
      <p>0,18
CurieLM-V02-Mistral-V02</p>
      <p>Mistral-7b-instruct-V02</p>
      <p>We can now observe that our CurieLM model is far more efficient than GPT4 and significantly
more efficient that Mistral 7b (our base model). Please note that for this chart we assume that GPT4
have 200b parameters which is a low estimation. One key point in the explanation of this higher
efficiency is to notice that even though GPT provides answer with higher accuracy, it does so using
a much larger number of parameters, leading to an overall ratio being lower. In other words, CurieLM
presents a higher ‘per parameter’ accuracy. We can go further in this improvement by increasing
the input context sent to our CurieLM model. This input context can be dynamically modified with
user information and with a nuclear ontology which will enrich the context of the question. This
context enrichment by ontology will consist of extracting keywords from the question to filters
relevant branch and nodes to a nuclear ontology (Table 1).</p>
      <sec id="sec-5-1">
        <title>What role does civil I’m a civil engineer</title>
        <p>engineering play in the working in nuclear
optimization of industry for an
thermal efficiency in a electrical French
nuclear power plant? provider.</p>
        <p>Context: [document 1,
document 2, document
3]
Question + RAG +
user information +</p>
        <p>ontology
enrichment.
(CurieLM model +</p>
        <p>KG tool)</p>
        <p>I’m a civil engineer
working in nuclear
industry for an
electrical French
provider.</p>
      </sec>
      <sec id="sec-5-2">
        <title>What role does civil What role does civil</title>
        <p>engineering play in the engineering play in the
optimization of optimization of
thermal efficiency in a thermal efficiency in a
nuclear power plant? nuclear power plant?
Context: [document 1, Similar concepts:
document 2, document Reactor Core Design,
3] Heat Transfer</p>
        <p>Systems, Cooling
System Design, Waste
Heat Recovery.</p>
        <p>Context: [document 1,
document 2, document
3]</p>
        <p>This method will automatically increase the input context without changing the user’s
experience. Larger input context will significantly improve the quality of the generated answer.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>The CurieLM project has shown that operating a fine tuning of a “small” LLM, by using a RAG
architecture and by extending the input context sent to a LLM might be an interesting way to
optimize the trade-off between computer power and generated answers quality. In other words, in a
computing resource-constrained paradigm which is often the case in engineering, using fine-tuning
constitutes a way to further improve overall quality, and accuracy without increasing the computing
power.</p>
      <p>The overall results of these earlier stage results are quite promising but can be improved by:</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Minglu</given-names>
            <surname>Wang</surname>
          </string-name>
          , Mingguang Zheng,
          <string-name>
            <surname>Lin</surname>
            <given-names>Tian</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhongming Qiu</surname>
            ,
            <given-names>Xiaoyan Li</given-names>
          </string-name>
          , (
          <year>2017</year>
          )
          <article-title>A full life cycle nuclear knowledge management framework based on digital system</article-title>
          ,
          <source>Annals of Nuclear Energy</source>
          , Volume
          <volume>108</volume>
          ,
          <year>2017</year>
          , Pages
          <fpage>386</fpage>
          -
          <lpage>393</lpage>
          , ISSN 0306-4549, https://doi.org/10.1016/j.anucene.
          <year>2017</year>
          .
          <volume>04</volume>
          .047.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Samuel</given-names>
            <surname>Carrara</surname>
          </string-name>
          (
          <year>2020</year>
          )
          <article-title>Reactor ageing and phase-out policies: global and regional prospects for nuclear power generation, Energy Policy</article-title>
          , Volume
          <volume>147</volume>
          ,
          <year>2020</year>
          , 111834, ISSN 0301-4215, https://doi.org/10.1016/j.enpol.
          <year>2020</year>
          .
          <volume>111834</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Jennex</surname>
            ,
            <given-names>M. E.</given-names>
          </string-name>
          (
          <year>2005</year>
          ). What is KM?
          <source>International Journal of Knowledge Management</source>
          ,
          <volume>1</volume>
          (
          <issue>4</issue>
          ), i-iv.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pablos</surname>
            ,
            <given-names>P.O.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Qi</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <year>2012</year>
          .
          <article-title>Enterprise knowledge management model based on China's practice and case study</article-title>
          .
          <source>Comput. Hum. Behav</source>
          .
          <volume>28</volume>
          (
          <issue>2</issue>
          ),
          <fpage>324</fpage>
          -
          <lpage>330</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Jain</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Meenachi</surname>
            <given-names>D.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Venkatraman</surname>
            <given-names>D.B.</given-names>
          </string-name>
          (
          <year>2020</year>
          ), arXiv preprint arXiv:
          <year>2003</year>
          .13821
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Devlin</surname>
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chang</surname>
            <given-names>M.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Toutanova</surname>
            <given-names>K.</given-names>
          </string-name>
          (
          <year>2018</year>
          ), arXiv preprint arXiv:
          <year>1810</year>
          .04805
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Acharya</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Munikoti</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hellinger</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smith</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wagle</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horawalavithana</surname>
            <given-names>S.</given-names>
          </string-name>
          (
          <year>2023</year>
          ), arXiv preprint arXiv:
          <volume>2310</volume>
          .
          <fpage>10920</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>Kernan</given-names>
            <surname>Freire</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Foosherian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Wellsandt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Ruiz-Arenas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            , &amp;
            <surname>Niforatos</surname>
          </string-name>
          ,
          <string-name>
            <surname>E.</surname>
          </string-name>
          (
          <year>2024</year>
          ).
          <article-title>Knowledge sharing in manufacturing using LLM-powered tools: user study and model benchmarking</article-title>
          .
          <source>Frontiers in Artificial Intelligence</source>
          ,
          <volume>7</volume>
          ,
          <fpage>1293084</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Bouhoun</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Allali</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cocci</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Assaad</surname>
            ,
            <given-names>M. A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Plancon</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Godest</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          , ... &amp;
          <string-name>
            <surname>Plana</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          (
          <year>2024</year>
          ).
          <article-title>CurieLM: Enhancing Large Language Models for Nuclear Domain Applications</article-title>
          .
          <source>In EPJ Web of Conferences</source>
          (Vol.
          <volume>302</volume>
          , p.
          <fpage>17006</fpage>
          ).
          <source>EDP Sciences.</source>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>