<!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>Implementing semantic technologies in materials science and engineering</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Marta Dembska</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Oliver Helle</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Itisha Yadav</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Diana Peters</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>German Aerospace Center (DLR), Institute of Data Science</institution>
          ,
          <addr-line>Jena</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>German Aerospace Center (DLR), Institute of Materials Research</institution>
          ,
          <addr-line>Cologne</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The Materials Science and Engineering (MSE) field is an interdisciplinary branch of engineering characterized by high volumes of heterogeneous data, which also serve as inputs for other fields reliant on materials. While semantic technologies are already utilized in various research areas to address data management challenges, their adoption in MSE is still in its early stages. This paper provides an overview of data management issues in MSE, existing semantic technologies, and the potential application of these technologies to address those issues. This leads to a roadmap for the implementation of semantic technologies in MSE.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Materials Science and Engineering</kwd>
        <kwd>Semantic Technologies</kwd>
        <kwd>Data Management</kwd>
        <kwd>Interoperability</kwd>
        <kwd>Ontologies</kwd>
        <kwd>Large Language Models</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>Science generates vast amounts of data. Before investing efort and money in the generation of
new datasets (e.g. by conducting experiments), it would be useful to find existing datasets that
already address the scientific question at hand. However, the sheer volume of data makes this a
daunting task, akin to searching for a needle in a haystack. Furthermore, the use of diferent
schemas to encode and describe data complicates the search process.</p>
      <p>
        To address this, the FAIR principles (Findable, Accessible, Interoperable, Reusable) were
proposed to enhance data sustainability [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Semantic Web technologies are the primary means
of implementing these principles, although their application varies significantly across scientific
domains. In this paper, we focus on the use of semantic technologies in the MSE domain, explore
the reasons why adoption should increase, and how this can be achieved efectively.
      </p>
      <p>MSE operates within a data-centric sphere, generating diverse datasets aimed at
advancing manufacturing technologies and detailing material structures along with their relevant
parameters. The sharing of this data, however, remains a challenge due to a lack of
documentation, of standardized usage of Research Data Management (RDM) practices in the field, and
others. Despite the rapid evolution of technology, the process of collecting new data in MSE
still heavily relies on loosely defined analogue processes, even if the data products are, in the
end, digital. Moreover, the absence of proper infrastructure, such as centralized databases for
both data products and metadata, hampers presesrvation of this data. Scientific findings are
often disseminated without establishing a clear link to the underlying data or software utilized
in their generation, and there is a notable lack of integration with well-defined licenses or
policies governing their usage. The absence of formalized processes and detailed descriptions
poses significant challenges in conducting follow-up research, reproducing results, identifying
potential sources of errors and workflow bottlenecks, and validating research findings.</p>
      <p>Descriptive, process- and domain-specific metadata are typically encapsulated either in only
human-readable resources or digital artifacts that are not machine-actionable. The
multidisciplinary nature of MSE compounds the issue of a lack of common and shared representations
for material knowledge, e.g., by ontologies, which are still insuficient in this field.</p>
      <p>Laboratory metadata in MSE manifests in various forms, ranging from handwritten notes in
laboratory notebooks or paper protocols to semi-digital lists and fully digital, yet not necessarily
machine-readable or -actionable, data files. The adoption of electronic laboratory notebooks
remains minimal. These factors collectively make it exceedingly challenging to analyze scientific
laboratory workflows in MSE or employ process records in automated data analysis processes.</p>
      <p>In this paper, we will outline how the majority of the MSE community’s data management
challenges can be addressed through the incorporation of existing semantic technologies.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related work on semantic technologies in MSE</title>
      <p>
        Currently, numerous national and international initiatives and consortia in MSE aim to establish
semantic technologies, such as shared vocabularies, metadata schemas, and ontologies. Notable
examples include the European Materials Modelling Council (EMMC) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], National Research
Data Infrastructure (NFDI) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] represented by its consortia MatWerk [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] and FAIRmat [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],
Platform MaterialDigital [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], Materials Genome Initiative (MGI) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], DICE Materials Data Platform
[
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], Diadem materials exploratory [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], materplat [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], Materials Commons [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], building the
Prototype Open Knowledge Network Program [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], and re3data [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
      </p>
      <p>
        The first comprehensive review of ontologies in MSE, focusing on Domain-Level Ontologies
(DLOs), was recently published by De Baas et al. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Among the most widely used
TopLevel Ontologies (TLOs) in MSE are the Basic Formal Ontology (BFO) [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], the Elementary
Multiperspective Material Ontology (EMMO) [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], the Semantiscience Integrated Ontology (SIO)
[
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], and the Suggest Upper Merged Ontology (SUMO) [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. These TLOs provide a framework
for developing semantically consistent DLOs by ofering general concepts for their development.
Of the 43 analyzed DLOs, 21 reuse EMMO, 10 BFO, 2 SIO, and 1 SUMO, respectively. The
remaining 10 do not reuse any of the four mentioned TLOs. Therefore, most DLOs in MSE (48%)
are currently aligned with EMMO [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
      </p>
      <p>
        Currently, there is only one repository focused on MSE ontologies called MatPortal [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ],
which covers 30 MSE ontologies. IndustryPortal also includes MSE ontologies, among others
[
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. Additionally, NFDI ofers the NFDI4Ing Terminology Service, which provides an ontology
repository for industrially relevant ontologies, but contains only a few MSE ontologies [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ].
      </p>
      <p>
        Ontologies are often used as the schema (T-box) component of a Knowledge Graph (KG),
which is then populated with domain-specific data, such as from experiments. Documents can
also contain relevant data or metadata from experiments. One way to populate KG with
information extracted from documents, are Large Language Models (LLMs). Ligabue et al. address
open information extraction on textual documents by creating sub-graphs from documents
and merging them into a larger KG [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]. Kesri et al. construct a KG using the T-box to define
the entities and relationships to extract from text [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. A sub-category of LLM that introduce
attention mechanisms are transformers [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]. These can be used for text generation, translation,
classification, etc. Most of the work in this area, however, focuses on text consisting of sentences,
while in engineering domains like MSE documents often contain semi-structured information
like tables and bullet points.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Challenges adopting semantic technologies in MSE</title>
      <sec id="sec-3-1">
        <title>3.1. Limited ontology development expertise</title>
        <p>Domain experts in MSE often lack the knowledge and experience required for developing usable
and semantically correct ontologies. Since properly educated ontology developers are not readily
available, the domain experts in MSE are often solely responsible for developing, implementing,
and testing semantic technologies for their everyday work. The missing knowledge itself might
already result in sub optimal semantic artifacts with issues such as ambiguity, semantic conflicts,
and low interoperability. Furthermore, taking simultaneously a domain expert and an ontology
developer role might cause conflicts of interest between the roles. In these cases the domain
expert role is often dominant, due to the higher amount of experience in it, which might lead to
decisions that are sound from the domain perspective, but semantically incorrect. Furthermore,
having little experience in the ontology developer role, the domain expert is often not aware of
these consequences.</p>
        <p>
          This raises the question why the required experience and knowledge is lacking. First, the
adoption of ontologies in MSE is still in its early stages, explaining the lack of experience.
Second, acquiring the required knowledge is not straightforward. Directly learning from
examples of other domains that have progressed further in adopting ontologies, e.g. biomedical
domains, requires a good understanding of the respective domains. Third, domain-agnostic
ontology development methodologies are not well standardized, which poses a challenge for
the inexperienced ontology developer. While there are multiple ontology development
methodologies available and in use, they all share common roots and core processes. However, most
common frameworks (such as METHONTOLOGY [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ], On-To-Knowledge [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ], DILIGENT [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ],
or SAMOD [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ], just to name a few), even if often straightforward and lightweight, do not
adequately address modern challenges related to ontology reuse, community development, and
maintenance. Some of the methodologies have not been updated for a long while, have never
been adopted for practical use for ontology development by domain experts, or their practical
applicability has never been published and is thus unknown to the public. Due to these
dificulties and the lack of expertise in ontology development by the domain experts, the developed
ontologies often lack in quality. This is especially problematic when more complicated issues
arise due to development activities such as ontology reuse.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Ontology reuse</title>
        <p>
          There is an understanding of the necessity for and usefulness of interoperability of ontologies
in the MSE domain. However, finding suitable reusable ontologies, evaluating their quality, and
assessing their applicability are tasks typically within the expertise of semantic technology
specialists such as ontology developers. Despite the abundance of existing ontologies, locating a
specific one that fulfills the requirements to be reused for a given use case can be challenging. In
heterogeneous fields like MSE, domain ontologies, even when developed as part of an initiative or
consortium, are frequently created independently of other initiatives. This lack of coordination
between the initiatives makes these ontologies challenging to discover or harmonize, which is
especially important in case of intersecting domains. While ontology repositories that aid in
ifnding MSE ontologies exist, they are not well connected with each other and provide little
information about vital aspects like scope and addressed topics of the ontologies, which are
important to consider when reusing ontologies. Consequently, the concepts of ontologies are
ifndable, but it requires efort and expertise to assess how these concepts are related to the topics
one wants to address with ontology reuse. Moreover, owing to the often necessarily pragmatic
approach used in ontology development in MSE, the developed ontologies are often not rich
or explicit in their semantics, ofering only taxonomic relationships, and lack documentation
of the developed concepts [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. This further compromises the findability of ontologies due to
missing concept definitions, only allowing ambiguous interpretations of the respective semantic
artifacts [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ], thus complicating identification of relevant concepts.
        </p>
        <p>
          Finding reusable ontologies is often further complicated, because it may not be possible to find
a single ontology that meets all given requirements. One option is to reuse multiple ontologies
to cover the requirements while maintaining high interoperability. However, this leads to
multiple challenges regarding their semantic compatibility, which possibly results in the need
to repeatedly align the ontologies during their integration. TLOs ofer a semantic framework
for harmonization and integration of DLOs [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ]. However, DLOs in MSE are sometimes not
based on a TLO, or based on multiple TLOs [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. The latter case can cause complex conflicts
during DLO integration since concepts from diferent TLOs are often based on foundationally
diferent assumptions. As a result, implications for the semantic compatibility of DLO concepts
based on diferent TLOs can be hard to grasp, even for experienced ontology developers.
        </p>
        <p>
          Furthermore, it might not be possible to find required subdomains for a particular use case, or
the available ontologies of the subdomain are not interoperable with other required subdomains.
While the former aspect may be attributed to generally incomplete and heterogeneous coverage
of MSE subdomains, the latter is a consequence of the lack of harmonization endeavors between
subdomains [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ].
        </p>
        <p>The last group of challenges regarding the compatibility of semantic artefacts between
diferent DLOs is caused by the inconsistent use of terminology and semantics. For example,
two concepts from diferent DLOs might have the same label, but actually refer to diferent
semantic concepts - or vice versa. This example becomes especially challenging, when the
semantic concepts also lack an elucidating definition and descriptions, which may lead to
ambiguous semantic concepts. While the structure of the DLOs can help decrease ambiguity of
these concepts, the pragmatically structured DLOs in MSE often do not contain the required
semantic richness to do so.</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Standardizing laboratory documentation</title>
        <p>Laboratory work documentation is essential to ensure accurate replication, reproducibility,
and traceability of experiments. At the same time, its preparation is a time-consuming and
tedious task. Meticulous records of experimental procedures facilitate eficient data analysis
and collaboration by enabling researchers to build on existing work. It is also necessary to meet
regulatory requirements in the laboratory environment. However, diversity in documentation
formats and limited use of Electronic Laboratory Notebooks (ELNs) complicate standardization
eforts and the digitalization of laboratory (meta)data in MSE. Non-unified documentation
practices and often manual (meta)data acquisition produce digital artifacts that have limited
reusability, even for their original authors. Since metadata is not always connected to their
related data, the establishment of meaningful relationships between datasets is hindered as well.
This especially applies to process-specific records, where, without a semantic model of laboratory
processes in place, the result is only artifacts of workflow runs lacking data provenance or
data lineage for specific data products. The systematic use of Persistent Identifiers ( PIDs) for
samples, equipment, and other elements of laboratory processes is also insuficient, itself not
preventing poor metadata quality associated with these elements. Moreover, if MSE input
data does not align with FAIR principles, it becomes dificult to produce FAIR data outputs.
Manual, unstructured documentation is time-consuming and ineficient, yet researchers and
laboratory technicians often resist adopting new technologies due to perceived complexity
and the significant time required for implementation. The high investment in time, money,
and expertise needed to implement semantic technologies presents a considerable barrier for
many laboratories. Furthermore, the complexity of MSE data, which is often highly specialized,
complicates mapping to existing semantic schemas. Establishing and maintaining relevant
ontologies is resource-intensive, posing additional challenges, as noted in Sections 3.1 and 3.2.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Addressing the challenges</title>
      <sec id="sec-4-1">
        <title>4.1. Standarization and interoperability</title>
        <p>
          Adhering to a well-defined methodology in ontology development ensures high quality and
reusability of the final product by providing structured guidelines for consistent design, rigorous
validation to catch errors early, and providing systematic documentation to support maintenance
and interoperability with other ontologies. This aspect is particularly relevant for domain
experts who are new to ontology development, as predicting potential issues in ontology
development can be challenging for them. The Linked Open Terms (LOT) methodology [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ], to
our best knowledge, is the first ontology development methodology specifically oriented towards
ontology publication using semantic web and FAIR principles. It provides users with practical
guidance and tools, which are particularly beneficial for domain experts transitioning into the
role of ontology developer, navigating the complexities associated with lack of experience in
ontology development. This methodology was developed using established practices and aligns
ontology development with agile software practices by using sprints and iterations. It divides
the entire iterative process into four main steps: requirements specification, implementation,
publication, and maintenance, making task division more accessible for domain experts acting
as ontology developers. While domain knowledge is essential for the first two steps, domain
experts not advanced in version control best practices can share the latter two steps with
an ontology expert or IT specialist without domain knowledge. This approach mitigates
challenges arising from potential role conflicts. The methodology improves the structure of the
development process, enhancing task granularity and accessibility throughout the steps. It ofers
practical advice on formulating competency questions, defines core ontology elements during
the conceptualization phase, and helps to decide between self-modeling and reusing concepts
from other ontologies. These aspects address common risks of potentially low quality outputs
of the ontology development process in MSE, resulting from lack of extensive experience in
ontology development among domain experts taking this role.
        </p>
        <p>
          LOT has been proven efective across a selection of diverse projects, covering a range of
applications and domains [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ], positioning it as a robust candidate for a domain-agnostic
standard approach to ontology development, with high potential for adoption in such diverse
domains as MSE. It introduces activities such as ontology publication, along with practical
tips and recommendations, which are critical as other methodologies may not fully align with
modern standards. Moreover, the methodology significantly enhances ontology reuse and
tooling, particularly beneficial and relevant for heterogeneous domains like MSE. Establishing
a dedicated framework for ontology development based on iterative processes, harmonization,
and ontology reuse within this framework proves more eficient as it reduces redundancy in
development eforts, and ensures consistency across ontology development projects. Adopting
LOT widely in MSE has the potential to establish a standardized workflow for ontology design,
bridging the gap between domain experts and ontology developers through structured guidelines
and processes. By providing specific modeling guidelines based on established ontologies, LOT
can serve as a model for other ontology development initiatives, fostering alignment and
integration across diferent projects. This approach not only promotes consistency but also
enhances the overall quality of ontologies developed within these diverse initiatives.
        </p>
        <p>
          Meanwhile, to enhance the interoperability of DLOs in MSE, concepts from a common TLO
should be reused to provide a base harmonisation of the DLO concepts. If DLOs use diferent
TLOs, it is suggested to engineer bridge concepts [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. Interoperability between hard to align
ontologies can also be established on data level. For example, the I-ADOPT [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ] Framework
ontology provides concepts to establish interoperability on a level of existing variable description
models. This can provide standardized interoperability on a variable level while mitigating
semantic conflicts on other levels. Variables are often important concepts in MSE ontologies
such as material properties, process parameters, and measurement results.
        </p>
        <p>
          Besides manual ontology development, there are approaches to enhance ontologies
(semi-)automatically. Ontology Learning (OL) is a field of research in Artificial Intelligence ( AI) and
knowledge engineering. LLM-based OL techniques have shown to perform better than
traditional ones on unstructured text to extract significant and domain relevant concepts and
their inter-dependencies [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ]. Work by da Silva et al. further explores how prompting with
LLMs afect the ontology generation and found the results to be promising, thereby generating
ontologies which are error-free [
          <xref ref-type="bibr" rid="ref33">33</xref>
          ]. LLMs in general have shown to perform better than
traditional supervised learning-based techniques across various domains in an out-of-the-box
manner, i.e., without having the need for finetuning to attain automation. However, for
performing domain-specific tasks within scientific domains like MSE, domain knowledge has to be
integrated within LLMs to get optimal results and better domain relevancy.
        </p>
        <p>
          KGs are, unlike ontologies, meant to contain also entity-level data. Modelling KGs is even more
time-consuming than modeling ontologies. Information Extraction (IE) focuses on extracting
information from documents, e.g., from experiment protocols or from data sheets. KGs can
subsequently be enriched by this extracted information to reduce manual efort and increase
scalability. To enrich KGs with IE, triples must be generated and incorporated into the KG, a
process known as KG fusion or KG population. A typical IE task, comprising of sub-tasks like
entity extraction and relation extraction, has shown to achieve better performance using
out-ofthe-box LLMs with correct prompting techniques than with model finetuning [
          <xref ref-type="bibr" rid="ref34">34</xref>
          ]. In addition
to IE, LLMs can also be used for KG population by creating KG embeddings [
          <xref ref-type="bibr" rid="ref35">35</xref>
          ]. However, to
enable LLMs to identify domain specific entities and concepts, domain ontologies are required.
By using domain ontologies as the ground-truth, LLMs can be prompted to do entity extraction.
As they are probabilistic models, LLMs inherently lack factual reliability. Constraint decoding
is therefore applied to control the output of the LLM. It is a way of integrating ontologies
with LLMs to make them "speak" a domain specific language. Luo et al. use ontology-based
constraint decoding within LLMs to generate comparatively less noisy training data for the task
of named entity recognition in resource-scarce domains [
          <xref ref-type="bibr" rid="ref36">36</xref>
          ]. Prompt engineering represents
another approach, integrating ontologies into the LLM prompts to instruct LLMs to perform a
particular task. Mihindukulasooriya et al. propose a prompting framework for constructing
KGs using ontologies and LLMs [
          <xref ref-type="bibr" rid="ref37">37</xref>
          ]. The ontology is supplied to the prompt, which is used to
instruct the LLM. Therefore, LLMs can ofer a boost to IE and KG enrichment for the domain of
MSE using domain-ontologies to prevent hallucinations.
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Technological advancement in laboratory practices</title>
        <p>
          Despite the significant variations among subdomains within MSE, there are noticeable parallels
in laboratory processes across the domain. Therefore, establishing unified frameworks for
collecting records of these processes can be done with a relatively low efort. Introducing
a process ontology, with a particular focus on gathering process provenance records in a
uniform format, can formalize these procedures. Utilizing PROV-O [
          <xref ref-type="bibr" rid="ref38">38</xref>
          ] and incorporating its
extension, the P-Plan Ontology [
          <xref ref-type="bibr" rid="ref39">39</xref>
          ], can efectively address this need, ensuring standardized
documentation of processes across the domain. Such unified records would greatly facilitate the
analysis of process bottlenecks, identification of synergies, and areas for improvement across
MSE subdomains and the field as a whole. Maintaining provenance records of workflow runs
also enables predictions for similar runs in the future, such as expected runtime or resources
required. Workflow provenance can also be used to detect outliers in workflow runs. A
standardized framework for process description, based on a well recognized model, makes
it easier to incorporate domain knowledge with the use of DLOs. Such a unified process
ontology can not only address the issue of diversity in laboratory documentation practices but
also ensure the FAIRification of output data products. It would be achieved by connections
between provenance information and the elements of laboratory workflows (e.g. inputs, outputs,
metadata of samples or equipment).
        </p>
        <p>
          The semantic description of laboratory processes aligns well with the utilization of ELNs. To
overcome resistance to developing and implementing new technologies in the community, one
should be considerate when choosing a suitable ELN. First, it should reduce the efort necessary
for eficient and easy manual forms population while reducing the number of errors. This can
be achieved by field restrictions, such as drop-down menus and other forms of assistance in
free text entries, such as semantic annotation of the content. Second, the implementation of
ontologies is necessary to semantically annotate the entries or cross-reference sub-elements
of a given form, which can be especially useful for automating the ELN use. ELN Finder [
          <xref ref-type="bibr" rid="ref40">40</xref>
          ]
is a tool designed to help identify a suitable ELN for a particular (sub)domain and use case. It
supports a broad range of selection criteria, including the ability to define custom templates
or device connections, customize the user interface, choose the type of license, and utilize
controlled vocabularies. A limited number of ELNs integrate ontologies for data annotation
(e.g., Chemotion ELN [
          <xref ref-type="bibr" rid="ref41">41</xref>
          ]) or to generate semantically annotated forms (e.g., Herbie [
          <xref ref-type="bibr" rid="ref42">42</xref>
          ]).
These and other ELNs suitable for use in MSE are part of the ELN Consortium [
          <xref ref-type="bibr" rid="ref43">43</xref>
          ], which
aims to establish common specifications for data and metadata exchange between diferent
ELNs. Additionally, ontology use for form creation can also enable the generation of digital
laboratory work protocols and other documents automatically. Once semantically annotated
with an ontology, ELN records can be directly stored in a KG without requiring additional
post-processing. It is important to include PIDs utilization while automating the ELN use. Even
without full FAIRification of laboratory data, PIDs can serve as a minimum form of identification
of workflow artifacts, including physical data, when implementing a process ontology. Reuse of
provenance ontologies also addresses crucial aspects such as the reproducibility of a particular
process run, comparison between diferent workflow runs, and visualization of process records.
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion and outlook</title>
      <p>We have given an overview, which and how semantic technologies can be used to tackle data
management challenges in MSE, including the domain specific dificulties in doing so. To show
actual results based on this theoretical roadmap, we started a project called "Ontology-based
Data Integration and eXploration" (ODIX). In ODIX, we re-use and create ontologies in the
MSE domain, based on the LOT methodology. These ontologies are then used to guide LLMs in
information extraction from documents. At the same time, the ontologies build the T-Box of a
KG, which gets enriched with the information extracted from documents. The information in
the KG is consequently well described to be used as input for further applications.</p>
      <p>A key application in ODIX is a visual exploration tool that allows domain experts to compare
information across diferent process steps of the same material probe or between diferent runs
of the same process — all formerly only stored in documents. The project involves collaboration
between computer scientists (primarily semantic experts) and domain experts (mostly in the
area of MSE). Evaluation of the results will be conducted by the domain experts with outcomes
to be published as the project advances. We look forward to seeing further practical applications
of the methodologies and processes outlined in this paper.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>M. D.</given-names>
            <surname>Wilkinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumontier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I. J.</given-names>
            <surname>Aalbersberg</surname>
          </string-name>
          , G. Appleton,
          <string-name>
            <given-names>M.</given-names>
            <surname>Axton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Baak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Blomberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-W.</given-names>
            <surname>Boiten</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. B. da Silva</given-names>
            <surname>Santos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. E.</given-names>
            <surname>Bourne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Bouwman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. J.</given-names>
            <surname>Brookes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Clark</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Crosas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Dillo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Dumon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Edmunds</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. T.</given-names>
            <surname>Evelo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Finkers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>GonzalezBeltran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. J.</given-names>
            <surname>Gray</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Groth</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Goble</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. S.</given-names>
            <surname>Grethe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Heringa</surname>
          </string-name>
          , P. A. '
          <string-name>
            <surname>t Hoen</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Hooft</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Kuhn</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Kok</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Kok</surname>
            ,
            <given-names>S. J.</given-names>
          </string-name>
          <string-name>
            <surname>Lusher</surname>
            ,
            <given-names>M. E.</given-names>
          </string-name>
          <string-name>
            <surname>Martone</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Mons</surname>
            ,
            <given-names>A. L.</given-names>
          </string-name>
          <string-name>
            <surname>Packer</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Persson</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Rocca-Serra</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Roos</surname>
            , R. van Schaik,
            <given-names>S.-A.</given-names>
          </string-name>
          <string-name>
            <surname>Sansone</surname>
            , E. Schultes,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Sengstag</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Slater</surname>
            , G. Strawn,
            <given-names>M. A.</given-names>
          </string-name>
          <string-name>
            <surname>Swertz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Thompson</surname>
            ,
            <given-names>J. van der</given-names>
          </string-name>
          <string-name>
            <surname>Lei</surname>
            , E. van Mulligen,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Velterop</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Waagmeester</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Wittenburg</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Wolstencroft</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Mons</surname>
          </string-name>
          ,
          <article-title>The FAIR Guiding Principles for scientific data management and stewardship</article-title>
          ,
          <source>Scientific Data</source>
          <volume>3</volume>
          (
          <year>2016</year>
          ). doi:
          <volume>10</volume>
          .1038/sdata.
          <year>2016</year>
          .
          <volume>18</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>The</given-names>
            <surname>European Materials Modelling Council</surname>
          </string-name>
          ,
          <year>2024</year>
          . URL: https://emmc.eu/.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>The</given-names>
            <surname>German National Research Data</surname>
          </string-name>
          <article-title>Infrastructure (NFDI) e</article-title>
          .V.,
          <year>2024</year>
          . URL: https://www. nfdi.de/association/?lang=en.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>NFDI-MatWerk</surname>
          </string-name>
          ,
          <source>Nationale Forschungsdateninfrastruktur für Materialwissenschaft &amp; Werkstoftechnik</source>
          ,
          <year>2024</year>
          . URL: https://nfdi-matwerk.de/.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5] FAIRmat,
          <string-name>
            <surname>Consortium</surname>
            <given-names>FAIRmat</given-names>
          </string-name>
          ,
          <year>2024</year>
          . URL: https://www.fairmat-nfdi.eu/fairmat/ about-fairmat/consortium-fairmat.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Material</surname>
            <given-names>Digital -</given-names>
          </string-name>
          <source>the material digitalization platform</source>
          ,
          <year>2019</year>
          . URL: https://materialdigital.de/.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Materials</given-names>
            <surname>Genome Initiative</surname>
          </string-name>
          ,
          <year>2014</year>
          . URL: https://www.mgi.gov/.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <article-title>[8] NIMS, DICE Materials Data Platform with Greatly Improved Data Collection</article-title>
          and
          <string-name>
            <given-names>Accumulation</given-names>
            <surname>Capabilities</surname>
          </string-name>
          ,
          <year>2023</year>
          . URL: https://www.nims.go.jp/eng/news/press/2023/01/202301170. html.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <article-title>[9] The 'Diadem' (materials) exploratory PEPR</article-title>
          ,
          <year>2023</year>
          . URL: https://www.cnrs.fr/en/pepr/ pepr-exploratoire
          <article-title>-diademe-materiaux.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>Plataforma</given-names>
            <surname>Tecnológica Española de Materiales Avanzados</surname>
          </string-name>
          y Nanomateriales,
          <year>2024</year>
          . URL: https://materplat.org/.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>Materials</given-names>
            <surname>Commons</surname>
          </string-name>
          ,
          <year>2020</year>
          . URL: https://materialscommons.org/.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>U.S.</given-names>
            <surname>National Science</surname>
          </string-name>
          <string-name>
            <surname>Foundation</surname>
          </string-name>
          ,
          <source>NSF invests $26</source>
          .
          <article-title>7 million in building the firstever prototype open knowledge network, 2023</article-title>
          . URL: https://new.nsf.gov/tip/updates/ nsf-invests
          <article-title>-first-ever-prototype-open-knowledge-network.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <source>[13] Registry of Research Data Repositories</source>
          ,
          <year>2020</year>
          . URL: https://www.re3data.org/.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>A. De Baas</surname>
            ,
            <given-names>P. D.</given-names>
          </string-name>
          <string-name>
            <surname>Nostro</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Friis</surname>
            , E. Ghedini, G. Goldbeck,
            <given-names>I. M.</given-names>
          </string-name>
          <string-name>
            <surname>Paponetti</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Pozzi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Sarkar</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Yang</surname>
            ,
            <given-names>F. A.</given-names>
          </string-name>
          <string-name>
            <surname>Zaccarini</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Toti</surname>
          </string-name>
          ,
          <article-title>Review and Alignment of Domain-Level Ontologies for Materials Science</article-title>
          ,
          <source>IEEE Access 11</source>
          (
          <year>2023</year>
          )
          <fpage>120372</fpage>
          -
          <lpage>120401</lpage>
          . doi:
          <volume>10</volume>
          .1109/access.
          <year>2023</year>
          .
          <volume>3327725</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>R.</given-names>
            <surname>Arp</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. D.</given-names>
            <surname>Spear</surname>
          </string-name>
          ,
          <article-title>Building Ontologies with Basic Formal Ontology</article-title>
          , MIT Press, Cambridge, MA,
          <year>2015</year>
          . doi:
          <volume>10</volume>
          .7551/mitpress/9780262527811.001.0001.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>The</given-names>
            <surname>Elementary Multiperspective Material Ontology</surname>
          </string-name>
          ,
          <year>2024</year>
          . URL: https://emmo-repo.github. io/.
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumontier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. J.</given-names>
            <surname>Baker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Baran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Callahan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Chepelev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Cruz-Toledo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. R.</given-names>
            <surname>Del Rio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Duck</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. I.</given-names>
            <surname>Furlong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Keath</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Klassen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. P.</given-names>
            <surname>McCusker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Queralt-Rosinach</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Samwald</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Villanueva-Rosales</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. D.</given-names>
            <surname>Wilkinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Hoehndorf</surname>
          </string-name>
          ,
          <article-title>The Semanticscience Integrated Ontology (SIO) for biomedical research and knowledge discovery</article-title>
          ,
          <source>Journal of Biomedical Semantics</source>
          <volume>5</volume>
          (
          <year>2014</year>
          ). doi:
          <volume>10</volume>
          .1186/2041-1480-5-14.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>I.</given-names>
            <surname>Niles</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Pease</surname>
          </string-name>
          ,
          <article-title>Towards a standard upper ontology</article-title>
          ,
          <source>in: Proceedings of the international conference on Formal Ontology in Information Systems - Volume</source>
          <year>2001</year>
          ,
          <article-title>FOIS01</article-title>
          , ACM,
          <year>2001</year>
          , pp.
          <fpage>2</fpage>
          -
          <lpage>9</lpage>
          . doi:
          <volume>10</volume>
          .1145/505168.505170.
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>Material</given-names>
            <surname>Open Laboratory MatPortal</surname>
          </string-name>
          ,
          <year>2021</year>
          . URL: https://matportal.org/.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>E.</given-names>
            <surname>Amdouni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sarkar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Jonquet</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. H.</given-names>
            <surname>Karray</surname>
          </string-name>
          ,
          <article-title>IndustryPortal: a common repository for FAIR ontologies in industry 4.0</article-title>
          , in: ISWC 2023 - 22nd International Semantic Web Conference, demo &amp; poster session, Athens, Greece,
          <year>2023</year>
          . URL: https://hal.science/hal-04207343.
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>NFDI4Ing</given-names>
            <surname>Terminology Service</surname>
          </string-name>
          ,
          <year>2021</year>
          . URL: https://terminology.nfdi4ing.de/ts/.
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>P. d. M.</given-names>
            <surname>Ligabue</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. A. F.</given-names>
            <surname>Brandão</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. M.</given-names>
            <surname>Peres</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. G.</given-names>
            <surname>Cozman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Pirozelli</surname>
          </string-name>
          ,
          <article-title>Applying a Context-based Method to Build a Knowledge Graph for the Blue Amazon</article-title>
          ,
          <source>Data Intelligence</source>
          <volume>6</volume>
          (
          <year>2024</year>
          )
          <fpage>64</fpage>
          -
          <lpage>103</lpage>
          . doi:
          <volume>10</volume>
          .1162/dint_a_
          <fpage>00223</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>V.</given-names>
            <surname>Kesri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Nayak</surname>
          </string-name>
          , K. Ponnalagu,
          <article-title>AutoKG - An Automotive Domain Knowledge Graph for Software Testing: A position paper</article-title>
          ,
          <source>in: 2021 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW)</source>
          , IEEE,
          <year>2021</year>
          , pp.
          <fpage>234</fpage>
          -
          <lpage>238</lpage>
          . doi:
          <volume>10</volume>
          .1109/icstw52544.
          <year>2021</year>
          .
          <volume>00047</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>A.</given-names>
            <surname>Vaswani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Shazeer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Parmar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Uszkoreit</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Jones</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. N.</given-names>
            <surname>Gomez</surname>
          </string-name>
          , L. u. Kaiser,
          <string-name>
            <surname>I. Polosukhin</surname>
          </string-name>
          , Attention is All you Need, in: I. Guyon,
          <string-name>
            <given-names>U. V.</given-names>
            <surname>Luxburg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Bengio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Wallach</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Fergus</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Vishwanathan</surname>
          </string-name>
          , R. Garnett (Eds.),
          <source>Advances in Neural Information Processing Systems</source>
          , volume
          <volume>30</volume>
          ,
          <string-name>
            <surname>Curran</surname>
            <given-names>Associates</given-names>
          </string-name>
          , Inc.,
          <year>2017</year>
          . URL: https://proceedings.neurips.cc/ paper_files/paper/2017/file/3f5ee243547dee91fbd053c1c4a845aa-Paper.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>M.</given-names>
            <surname>Fernández-López</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gómez-Pérez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. Juristo</given-names>
            <surname>Juzgado</surname>
          </string-name>
          ,
          <source>METHONTOLOGY: From Ontological Art Towards Ontological Engineering</source>
          (
          <year>1997</year>
          ). URL: https://oa.upm.es/5484/, ontology Engineering Group - OEG.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Studer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.-P.</given-names>
            <surname>Schnurr</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Sure</surname>
          </string-name>
          ,
          <article-title>Knowledge processes and ontologies</article-title>
          ,
          <source>IEEE Intelligent systems 16</source>
          (
          <year>2001</year>
          )
          <fpage>26</fpage>
          -
          <lpage>34</lpage>
          . doi:
          <volume>10</volume>
          .1109/5254.912382.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>H. S.</given-names>
            <surname>Pinto</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Tempich</surname>
          </string-name>
          , DILIGENT:
          <article-title>Towards a fine-grained methodology for DIstributed, Loosely-controlled and evolvInG Engineering of oNTologies</article-title>
          ,
          <source>in: ECAI</source>
          , volume
          <volume>16</volume>
          ,
          <year>2004</year>
          , p.
          <fpage>393</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>S.</given-names>
            <surname>Peroni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A Simplified</given-names>
            <surname>Agile</surname>
          </string-name>
          <article-title>Methodology for Ontology Development</article-title>
          , in: OWL: Experiences and
          <string-name>
            <surname>Directions-Reasoner</surname>
            <given-names>Evaluation</given-names>
          </string-name>
          : 13th International Workshop, OWLED 2016,
          <article-title>and</article-title>
          5th International Workshop, ORE 2016, Bologna, Italy, November
          <volume>20</volume>
          ,
          <year>2016</year>
          ,
          <source>Revised Selected Papers 13</source>
          , Springer, Springer International Publishing,
          <year>2017</year>
          , pp.
          <fpage>55</fpage>
          -
          <lpage>69</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -54627-
          <issue>8</issue>
          _
          <fpage>5</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29] ISO/IEC,
          <fpage>21838</fpage>
          -
          <lpage>1</lpage>
          :
          <year>2021</year>
          <article-title>(en), Information technology - Top-level ontologies (TLO) - Part 1: Requirements</article-title>
          , Standard, International Organization for Standardization, Geneva,
          <string-name>
            <surname>CH</surname>
          </string-name>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>M.</given-names>
            <surname>Poveda-Villalón</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Fernández-Izquierdo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Fernández-López</surname>
          </string-name>
          ,
          <string-name>
            <surname>R.</surname>
          </string-name>
          <article-title>García-Castro, LOT: An industrial oriented ontology engineering framework</article-title>
          ,
          <source>Engineering Applications of Artificial Intelligence</source>
          <volume>111</volume>
          (
          <year>2022</year>
          )
          <article-title>104755</article-title>
          . doi:
          <volume>10</volume>
          .1016/j.engappai.
          <year>2022</year>
          .
          <volume>104755</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>B.</given-names>
            <surname>Magagna</surname>
          </string-name>
          , I. Rosati,
          <string-name>
            <given-names>M.</given-names>
            <surname>Stoica</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Schindler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Moncoifé</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Devaraju</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Peterseil</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Huber</surname>
          </string-name>
          ,
          <article-title>The I-ADOPT Interoperability Framework for FAIRer data descriptions of biodiversity</article-title>
          ,
          <source>CoRR abs/2107</source>
          .06547 (
          <year>2021</year>
          ). doi:
          <volume>10</volume>
          .48550/ARXIV.2107.06547. arXiv:
          <volume>2107</volume>
          .
          <fpage>06547</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <given-names>H.</given-names>
            <surname>Babaei Giglou</surname>
          </string-name>
          ,
          <string-name>
            <surname>J. D'Souza</surname>
            ,
            <given-names>S. Auer,</given-names>
          </string-name>
          <article-title>LLMs4OL: Large Language Models for Ontology Learning</article-title>
          , in: International Semantic Web Conference, Springer,
          <year>2023</year>
          , pp.
          <fpage>408</fpage>
          -
          <lpage>427</lpage>
          . doi:
          <volume>10</volume>
          . 1007/978-3-
          <fpage>031</fpage>
          -47240-4_
          <fpage>22</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>L. M. V.</given-names>
            da
            <surname>Silva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Köcher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Gehlhof</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Fay</surname>
          </string-name>
          ,
          <article-title>On the Use of Large Language Models to Generate Capability Ontologies</article-title>
          ,
          <source>arXiv preprint arXiv:2404.17524</source>
          (
          <year>2024</year>
          ). doi:
          <volume>10</volume>
          .48550/ ARXIV.2404.17524.
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          [34]
          <string-name>
            <given-names>L.</given-names>
            <surname>Luo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.-F.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Hafari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Pan</surname>
          </string-name>
          ,
          <source>Reasoning on Graphs: Faithful and Interpretable Large Language Model Reasoning</source>
          , arXiv preprint arXiv:
          <volume>2310</volume>
          .01061 (
          <year>2023</year>
          ). doi:
          <volume>10</volume>
          .48550/ ARXIV.2310.01061.
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          [35]
          <string-name>
            <given-names>S.</given-names>
            <surname>Pan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Luo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <article-title>Unifying Large Language Models and Knowledge Graphs: A Roadmap</article-title>
          ,
          <source>IEEE Transactions on Knowledge and Data Engineering</source>
          <volume>36</volume>
          (
          <year>2024</year>
          )
          <fpage>3580</fpage>
          -
          <lpage>3599</lpage>
          . doi:
          <volume>10</volume>
          .1109/tkde.
          <year>2024</year>
          .
          <volume>3352100</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          [36]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Luo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Ke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Qi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Guo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <article-title>Boosting LLMS with Ontology-Aware Prompt for Ner Data Augmentation</article-title>
          , in: ICASSP 2024
          <article-title>-</article-title>
          2024 IEEE International Conference on Acoustics,
          <source>Speech and Signal Processing (ICASSP)</source>
          , IEEE, IEEE,
          <year>2024</year>
          , pp.
          <fpage>12361</fpage>
          -
          <lpage>12365</lpage>
          . doi:
          <volume>10</volume>
          .1109/icassp48485.
          <year>2024</year>
          .
          <volume>10446860</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          [37]
          <string-name>
            <given-names>N.</given-names>
            <surname>Mihindukulasooriya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Tiwari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. F.</given-names>
            <surname>Enguix</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lata</surname>
          </string-name>
          ,
          <article-title>Text2KGBench: A Benchmark for Ontology-Driven Knowledge Graph Generation from Text</article-title>
          , in: International Semantic Web Conference, Springer, Springer Nature Switzerland,
          <year>2023</year>
          , pp.
          <fpage>247</fpage>
          -
          <lpage>265</lpage>
          . doi:
          <volume>10</volume>
          .1007/ 978-3-
          <fpage>031</fpage>
          -47243-5_
          <fpage>14</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref38">
        <mixed-citation>
          [38]
          <string-name>
            <surname>The</surname>
            <given-names>PROV Ontology</given-names>
          </string-name>
          ,
          <year>2013</year>
          . URL: https://www.w3.org/TR/prov-o.
        </mixed-citation>
      </ref>
      <ref id="ref39">
        <mixed-citation>
          [39]
          <string-name>
            <surname>The P-PLAN Ontology</surname>
          </string-name>
          ,
          <year>2013</year>
          . URL: https://www.opmw.org/model/p-plan.
        </mixed-citation>
      </ref>
      <ref id="ref40">
        <mixed-citation>
          [40]
          <string-name>
            <given-names>ELN</given-names>
            <surname>Finder</surname>
          </string-name>
          ,
          <year>2024</year>
          . URL: https://eln-finder.ulb.tu-darmstadt.de.
        </mixed-citation>
      </ref>
      <ref id="ref41">
        <mixed-citation>
          [41]
          <string-name>
            <surname>Chemotion</surname>
            <given-names>ELN</given-names>
          </string-name>
          ,
          <year>2024</year>
          . URL: https://www.chemotion.net/docs/eln.
        </mixed-citation>
      </ref>
      <ref id="ref42">
        <mixed-citation>
          [42]
          <string-name>
            <given-names>F.</given-names>
            <surname>Kirchner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Eschke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.-L.</given-names>
            <surname>Höhme</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Meller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Foremny</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Held</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. A.</given-names>
            <surname>Sahim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Willumeit-Römer</surname>
          </string-name>
          , Herbie - The Semantic Laboratory Notebook &amp; Research Database.,
          <year>2024</year>
          . doi:
          <volume>10</volume>
          .5281/ZENODO.12205430.
        </mixed-citation>
      </ref>
      <ref id="ref43">
        <mixed-citation>
          [43]
          <string-name>
            <surname>ELN-Consortium</surname>
          </string-name>
          :
          <article-title>A consortium of ELN vendors</article-title>
          ,
          <year>2024</year>
          . URL: https://github.com/ TheELNConsortium.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>