<!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>Guiding LLM Generated Mappings with Lifecycle-Based Metadata: An Early Evaluation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sarah Alzahrani</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Declan O'Sullivan</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ADAPT Center, Trinity College Dublin</institution>
          ,
          <country country="IE">Ireland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Imam Mohammad Ibn Saud Islamic University (IMSIU)</institution>
          ,
          <country country="SA">Saudi Arabia</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>School of Computer Science and Statistics, Trinity College Dublin</institution>
          ,
          <country country="IE">Ireland</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Large Language Models (LLMs) are increasingly used to automate knowledge engineering tasks such as generating RDF mappings. While promising, their outputs often lack semantic precision, syntactic correctness, and contextual metadata. This paper investigates whether structured metadata aligned with the mapping lifecycle can improve the quality and reusability of LLM-generated mappings. We present a metadata model that covers key phases of the mapping process and integrate it into the MetaSEMAP tool to support context-aware prompting. Using real-world uplift scenarios, we compare RML outputs generated from unguided prompts with those informed by lifecycle metadata. Our initial findings show that guided prompts consistently produce syntactically valid, semantically rich, and FAIR-aligned mappings. These results highlight the potential of structured metadata to guide LLMs toward generating higher-quality and reusable semantic artifacts in knowledge graph construction.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Metadata</kwd>
        <kwd>Declarative mappings</kwd>
        <kwd>LLMs</kwd>
        <kwd>Mapping lifecycle</kwd>
        <kwd>Knowledge graphs</kwd>
        <kwd>Context engineering</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Declarative mappings like RML1 are essential for transforming structured data into RDF for use in
knowledge graphs. However, creating such mappings is a technically demanding task, often requiring
expertise in both syntax and domain-specific ontologies [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Recently, large language models (LLMs)
have shown promise in assisting with this task by generating knowledge graphs and mappings from
natural language descriptions [
        <xref ref-type="bibr" rid="ref2 ref3 ref4">2, 3, 4</xref>
        ]. Despite their capabilities, LLMs often struggle with producing
outputs that are semantically accurate, syntactically valid, and compliant with established standards [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],
and human-in-the-loop validation is often recommended to ensure quality and reliability.
      </p>
      <p>
        This paper explores whether incorporating structured metadata into LLM prompts can improve the
quality of generated mappings. This approach aligns with recent work in context engineering, which
focuses on enriching prompts with structured and task-specific context to enhance the reliability and
relevance of LLM outputs [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. We focus on a real-world scenario involving the creation of mappings
to uplift data from Ireland’s open data portal2.and demonstrate how metadata guidance, based on a
mapping lifecycle model, influences the outputs generated by gpt-3.5-turbo (via OpenAI API).
      </p>
      <p>The remainder of this paper is structured as follows: we review related work on declarative mappings,
metadata standards, and the role of LLMs in semantic data generation. We then introduce our
lifecyclebased metadata model and its integration into the MetaSEMAP prompting interface. Next, we present
the experiment design and results comparing guided and unguided prompt outputs. Finally, we conclude
the paper and outline future research directions.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Background and Related Work</title>
      <sec id="sec-2-1">
        <title>2.1. Declarative Mappings and Metadata Need</title>
        <p>
          Declarative mapping languages such as R2RML and its extension RML enable structured transformation
of heterogeneous data sources into RDF for use in knowledge graphs [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. These languages define how
data is semantically uplifted without requiring custom code. RML, in particular, supports various input
formats like CSV, JSON, and XML using the RML vocabulary in combination with query languages such
as XPath and JSONPath. Despite its expressiveness, authoring RML mappings remains a technically
demanding task. Tools like YARRRML [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] and documentation frameworks such as RMLDoc [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] aim to
simplify this process by ofering user-friendly syntaxes or structured documentation. However, the
lack of embedded metadata to describe the purpose, provenance, and context of mappings limits their
interpretability and reuse.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Metadata Standards for Mappings</title>
        <p>
          To enhance transparency and reusability, several metadata standards have been proposed.
Generalpurpose vocabularies like Dublin Core and DCAT provide terms for describing datasets and publishing
context. More specialized eforts, such as SSSOM [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ], focus on metadata for ontology alignments,
while MQV [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] supports the assessment of mapping quality. Recent initiatives like FAIR-IMPACT [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]
proposed metadata and best practices for describing mappings as FAIR Digital Objects, aiming to
improve their findability, accessibility, and interoperability. These eforts ofer valuable guidance on
core metadata elements such as provenance, mapping purpose, and versioning, but remain largely
conceptual and do not yet support a comprehensive, lifecycle-based framework. As a result, a unified
metadata model that cover the full mapping lifecycle including design, generation, documentation, and
reuse is still lacking. To address this, we propose a structured lifecycle-based metadata model that
captures key elements across five phases of mapping activities. This model, introduced and evaluated
in our earlier work [
          <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
          ], is further detailed later in the paper.
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3. Large Language Models in Semantic Mapping</title>
        <p>
          Large Language Models (LLMs), such as GPT-3 and GPT-4, have demonstrated the ability to generate
RDF triples, SPARQL queries, and declarative mappings such as RML from natural language inputs [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ].
This capability presents new opportunities for simplifying the knowledge graph construction process,
particularly for non-experts. However, while promising, the outputs of LLMs often lack semantic
precision and completeness. Studies have shown that LLM-generated mappings frequently omit critical
components such as input declarations, namespace prefixes, and join conditions, and they rarely include
metadata supporting provenance, reuse, or quality assessment [
          <xref ref-type="bibr" rid="ref14 ref2 ref3">14, 3, 2</xref>
          ]. Moreover, these mappings
may include hallucinated classes or properties that do not exist in the target ontology, making them
unreliable for use.
        </p>
        <p>To address these challenges, we propose a structured metadata-driven approach that guides LLMs
using context aligned with the mapping lifecycle. By injecting metadata such as the mapping’s purpose,
data source characteristics, design decisions, and provenance, we provide the model with
domainspecific constraints and intentions that help shape the generated outputs. This approach improves the
accuracy, interpretability, and reusability of the resulting mappings by grounding generation in explicit
and verifiable context.</p>
        <p>
          This aligns with emerging practices in context engineering [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ], where structured metadata and formal
vocabularies help constrain and contextualize LLM behavior to produce more accurate and consistent
outputs. In our case, the metadata model acts as a source of prompt structure, supporting reproducibility
and enhancing trust in LLM-assisted mapping generation.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Lifecycle Metadata Model</title>
      <p>
        To support high-quality and reusable semantic mappings, we proposed a lifecycle-based metadata model
that organizes metadata across five key phases: analysis, design, development, testing, and maintenance.
This model was first introduced in our earlier work [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] and later validated through a community study
with Semantic Web practitioners [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. It is implemented in the MetaMap tool [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], enabling structured
metadata capture through a guided interface.
      </p>
      <p>
        The model includes fields for describing the mapping purpose, input sources, stakeholders, design
decisions, tooling, validation outcomes, and publishing context. Table 1 presents a summary of the key
metadata fields grouped by lifecycle phase. The full specification is publicly available on GitHub [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ].
      </p>
      <p>In this paper, we extend the model’s use beyond documentation by incorporating selected fields into
LLM prompts. This approach evaluates whether structured metadata can guide LLMs to generate more
accurate, standards-compliant, and reusable RML mappings.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Methodology</title>
      <sec id="sec-4-1">
        <title>4.1. Experimental Setup</title>
        <p>To evaluate whether lifecycle-based metadata improves the quality of LLM-generated RML mappings,
we designed an experiment comparing two prompting strategies: (1) unguided prompts with only a task
description, and (2) guided prompts augmented with structured metadata. We used gpt-3.5-turbo via
the OpenAI Python SDK v1.0 (chat.completions.create) to generate RML outputs. All prompts
were submitted through a controlled interface (Figure 1) to ensure consistent model behavior and
prompt formatting across both guided and unguided conditions.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Mapping Scenarios</title>
        <p>We evaluate our approach using three real-world scenarios derived from publicly available datasets on
Ireland’s open data portal2. Full dataset links and mapping files are available in our GitHub repository 3.
In Scenario 1 (S1), we use the Counties, National Statutory Boundaries, 2019 dataset to convert a CSV file
containing administrative boundary data for Irish counties into RDF. Although the dataset includes
multiple attributes such as object IDs, area size, Irish names, and shape geometry, only a relevant subset
was selected for the purpose of the experiment.</p>
        <p>In Scenario 2 (S2), we use the G0421, Population per NUTS 3 Region dataset to convert a JSON file
containing population data for Irish regions into RDF. Although the dataset includes various statistical
ifelds such as region codes, units of measurement, and percentage values, only a relevant subset was
selected for the purpose of the experiment. The mapping focused on region identifiers, population
counts, and temporal attributes to construct RDF triples that reflect regional population distributions in
a given year.</p>
        <p>In Scenario 3 (S3), we use the CSO Electoral Divisions, National Statistical Boundaries, 2022 dataset to
convert a CSV file containing administrative division data for electoral districts in Ireland into RDF.
Although the dataset includes various attributes such as object IDs, Irish and English names, shape
geometry, and codes from multiple authorities, only a relevant subset was selected for the purpose of
the experiment. The mapping focused on modeling spatial hierarchy and containment relationships.
Each electoral division was assigned a hierarchical URI based on its ED_ID and linked to its parent
county and province using a custom property ex:containedIn.</p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Prompt Design</title>
        <p>
          To compare the efects of metadata guidance, each mapping scenario was submitted to gpt-3.5-turbo
using two types of prompts: unguided and guided. The unguided prompt included only a task description,
while the guided prompt was enriched with structured metadata drawn from our lifecycle-based model,
which defines 37 fields across five phases. We selected 17 fields most relevant to prompt-based mapping
generation, focusing on descriptors from the Analysis and Design phases (e.g., Purpose, Mapping Type,
Mapping Domain, Input Description, Final Design Decisions, Justification, and Quality Metrics). We also
included contextual publishing and output fields from the Maintenance phase such as Publisher Source,
Version Number, Version Date, Output Format, and Output Syntax, which clarify expected structure
and encourage standards compliance. These fields were chosen based on their impact on design-time
decisions and feedback from previous user studies [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] showing their relevance to mapping quality and
reuse.
        </p>
        <p>Fields from the Development and Testing phases (e.g., Tools, Mapping Algorithm, Testing Result) were
excluded as they relate to post-generation steps. Similarly, fields with limited influence on generative
quality (e.g., Risks, Stakeholder Background) were omitted. The selected metadata was embedded in
natural language form to simulate structured context engineering and guide the LLM in producing
syntactically valid, semantically rich, and reusable RML mappings. Table 2 shows an example of both
prompt types used in Scenario 1 (S1). The full prompt sets for Scenarios 2 and 3 are available in our
GitHub repository3.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Evaluation</title>
      <p>Each mapping was assessed based on three key dimensions. Correctness refers to whether the output is
syntactically valid RML and can be parsed without errors. Structure awareness evaluates how well the
mapping captures the structure of the input data, including the correct use of rml:logicalSource,
rml:referenceFormulation, and iterators. Semantic quality considers whether the mapping uses
meaningful classes, properties, and URIs aligned with domain semantics and whether it includes
relevant metadata to support reuse. Across all three scenarios, guided prompts produced mappings that
3Project repository: https://github.com/sarah-alzahrani/LLM.
were consistently more correct, structurally aware, and semantically richer than those from unguided
prompts. In particular, all guided prompts correctly used rml:logicalSource, specifying input type
and reference formulation (e.g., ql:CSV or ql:JSONPath), and included iterator when handling
JSON inputs. In contrast, unguided prompts often defaulted to rr:logicalTable, which is valid
R2RML syntax but insuficient for non-tabular or nested data. This distinction is important because
logicalSource is the required mechanism in RML for handling diverse data sources, and its absence
leads to incorrect or incomplete mappings, especially for formats like JSON. For example:
• Scenario 1 (Counties – CSV): The unguided mapping used rr:logicalTable, ignoring
CSVspecific reference formulation. The guided version used rml:logicalSource with ql:CSV,
along with appropriate classes and coordinate properties.
• Scenario 2 (Population – JSON): The unguided prompt omitted both the iterator and
JSON path references, resulting in an unusable mapping. The guided prompt correctly used
ql:JSONPath, specified the iterator, and aligned the schema with population data standards.
• Scenario 3 (Electoral Divisions – CSV): The unguided output lacked hierarchical URI structure
and containment logic. The guided version constructed meaningful URIs using region and division
identifiers, and modeled geographic relationships with custom and standard vocabularies.
These results highlight how metadata-enriched prompting helps LLMs handle diferent mapping
complexities by injecting contextual knowledge into generation. Guided prompts also produced reusable
outputs that included metadata blocks aligned with FAIR and provenance principles, which were
entirely missing from unguided versions. Overall, our initial evaluation shows that context-aware
prompting grounded in lifecycle metadata improves both the technical correctness and semantic value
of LLM-generated mappings, supporting better reuse, validation, and documentation. While this early
evaluation ofers qualitative insights, future work will expand the analysis with quantitative scoring,
completeness metrics, and broader use case coverage to more systematically validate the approach.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion and Future Work</title>
      <p>This study investigated the efect of lifecycle-based metadata guidance on the quality of RML mappings
generated by LLM. By comparing guided and unguided prompts, we observed that metadata-enriched
prompting significantly improves the syntactic accuracy, semantic richness, and standards compliance
of LLM-generated mappings. Guided prompts led to the consistent use of appropriate vocabularies,
correct handling of input formats, and the inclusion of metadata blocks that enhance provenance and
reuse. These initial findings support a context-aware approach that combines the generative flexibility
of LLMs with structured metadata to improve the reliability, interpretability, and reusability of semantic
outputs. In future work, we plan to extend this evaluation framework to additional mapping types,
compare performance across diferent LLMs, as well as investigate whether prompting LLMs to generate
declarative mappings (like RML) results in more reusable outputs than directly generating RDF triples.
Our initial findings highlight the value of structured metadata not just for documentation but as a guide
in prompt-based knowledge graph construction. As LLMs become embedded in semantic workflows,
the community must consider not only what outputs they generate but also how those outputs are
guided, contextualized, and made reusable for others.</p>
    </sec>
    <sec id="sec-7">
      <title>7. Acknowledgments</title>
      <p>The first author acknowledges financial support from Al Imam Mohammad Ibn Saud Islamic University
and the Saudi government — represented by the Royal Embassy of Saudi Arabia — Cultural Bureau in
Dublin. The second author is partially supported by the SFI ADAPT Research Centre (grant number
13/RC/2106_P2).</p>
    </sec>
    <sec id="sec-8">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the author used ChatGPT (GPT-4) and Grammarly for the purposes
of grammar improvements. All AI-generated content was thoroughly reviewed, edited, and validated
by the author, who takes full responsibility for the final manuscript and all its content.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A.</given-names>
            <surname>Dimou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. V.</given-names>
            <surname>Sande</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Colpaert</surname>
          </string-name>
          , E. Mannens,
          <string-name>
            <given-names>R.</given-names>
            <surname>Verborgh</surname>
          </string-name>
          , R. V. de Walle,
          <article-title>Rml: A generic language for integrated rdf mappings of heterogeneous data</article-title>
          ,
          <source>in: Proceedings of the 7th Workshop on Linked Data on the Web (LDOW)</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Freund</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Dorsch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Schmid</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Harth</surname>
          </string-name>
          ,
          <article-title>Mapping by example: Towards an rml mapping reverse engineering pipeline</article-title>
          ,
          <source>in: ESWC 2025 Workshop on Knowledge Graph Construction (KGCW)</source>
          ,
          <year>2025</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>M.</given-names>
            <surname>Hofer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Frey</surname>
          </string-name>
          , E. Rahm,
          <article-title>Towards self-configuring knowledge graph construction pipelines using llms - a case study with rml</article-title>
          ,
          <source>in: Proceedings of the 6th International Workshop on Knowledge Graph Construction (KGCW@ESWC)</source>
          ,
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>B.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , H. Soh, Extract, define, canonicalize
          <article-title>: An llm-based framework for knowledge graph construction</article-title>
          ,
          <source>arXiv preprint arXiv:2404.03868</source>
          (
          <year>2024</year>
          ). URL: https://arxiv.org/abs/2404.03868. doi:
          <volume>10</volume>
          .48550/arXiv.2404.03868,
          <source>proceedings of the 2024 Conference on Empirical Methods in Natural Language Processing.</source>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>V. K.</given-names>
            <surname>Kommineni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>König-Ries</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Samuel</surname>
          </string-name>
          ,
          <article-title>From human experts to machines: An llm supported approach to ontology and knowledge graph construction</article-title>
          ,
          <source>arXiv preprint arXiv:2402.11155</source>
          (
          <year>2024</year>
          ). URL: https://arxiv.org/abs/2403.08345.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>A.</given-names>
            <surname>Volkov</surname>
          </string-name>
          , What is context engineering?,
          <year>2024</year>
          . URL: https://blog.getzep.com/ what-is
          <string-name>
            <surname>-</surname>
          </string-name>
          context-engineering/.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>P.</given-names>
            <surname>Heyvaert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Dimou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Verborgh</surname>
          </string-name>
          , Yarrrml:
          <article-title>Yet another rml rendering language</article-title>
          ,
          <source>in: Proceedings of the 1st International Workshop on Knowledge Graph Construction (KGC</source>
          <year>2018</year>
          ), volume
          <volume>2160</volume>
          <source>of CEUR Workshop Proceedings</source>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>P.</given-names>
            <surname>Heyvaert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Dimou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Verborgh</surname>
          </string-name>
          , Rmldoc:
          <article-title>Generating documentation for declarative mapping rules</article-title>
          ,
          <source>in: Proceedings of the 22nd International Semantic Web Conference (ISWC</source>
          <year>2023</year>
          ), volume
          <volume>14265</volume>
          of Lecture Notes in Computer Science, Springer,
          <year>2023</year>
          , pp.
          <fpage>169</fpage>
          -
          <lpage>185</lpage>
          . doi:
          <volume>10</volume>
          .1007/ 978-3-
          <fpage>031</fpage>
          -41393-4_
          <fpage>11</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>N.</given-names>
            <surname>Matentzoglu</surname>
          </string-name>
          , et al.,
          <article-title>A simple standard for sharing ontological mappings (sssom</article-title>
          ),
          <source>Database</source>
          <year>2022</year>
          (
          <year>2022</year>
          )
          <article-title>baac035</article-title>
          . doi:
          <volume>10</volume>
          .1093/database/baac035.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>A.</given-names>
            <surname>Randles</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. C.</given-names>
            <surname>Junior</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
          </string-name>
          <article-title>O'Sullivan, A vocabulary for describing mapping quality assessment, refinement and validation</article-title>
          ,
          <source>in: 2021 IEEE 15th International Conference on Semantic Computing (ICSC)</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>425</fpage>
          -
          <lpage>430</lpage>
          . doi:
          <volume>10</volume>
          .1109/ICSC50631.
          <year>2021</year>
          .
          <volume>00076</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Le Franc</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Grau</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Juty</surname>
          </string-name>
          , G. Mejias,
          <string-name>
            <given-names>P.</given-names>
            <surname>Reed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Ramezani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Poveda-Villalón</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Garijo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Goble</surname>
          </string-name>
          , R. van Horik,
          <year>D4</year>
          .5
          <article-title>- Guidelines and methodology to create, document and share mappings and crosswalks (</article-title>
          <source>V1.1)</source>
          ,
          <source>Technical Report, FAIR-IMPACT</source>
          ,
          <year>2025</year>
          . URL: https://doi.org/10.5281/zenodo. 15111167. doi:
          <volume>10</volume>
          .5281/zenodo.15111167.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>S.</given-names>
            <surname>Alzahrani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Sullivan</surname>
          </string-name>
          ,
          <article-title>Towards a unified metadata model for semantic and data mappings</article-title>
          ,
          <source>in: Ontology Matching workshop at ISWC</source>
          <year>2022</year>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>S.</given-names>
            <surname>Alzahrani</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
          </string-name>
          <article-title>O'Sullivan, What metadata is needed for semantic and data mappings?</article-title>
          ,
          <source>in: 2023 IEEE 17th International Conference on Semantic Computing (ICSC)</source>
          ,
          <year>2023</year>
          , pp.
          <fpage>312</fpage>
          -
          <lpage>316</lpage>
          . doi:
          <volume>10</volume>
          .1109/ICSC56153.
          <year>2023</year>
          .
          <volume>00064</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>M.</given-names>
            <surname>Parciak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Vandevoort</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Neven</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Peeters</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Vansummeren</surname>
          </string-name>
          ,
          <article-title>Schema matching with large language models: An experimental study</article-title>
          ,
          <source>in: Proceedings of the VLDB 2024 Workshops, CEUR-WS</source>
          ,
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>S.</given-names>
            <surname>Alzahrani</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
          </string-name>
          <article-title>O'Sullivan, Metamap: Facilitating mapping reuse and lifecycle documentation</article-title>
          ,
          <source>in: 2024 IEEE 18th International Conference on Semantic Computing (ICSC)</source>
          ,
          <year>2024</year>
          , pp.
          <fpage>323</fpage>
          -
          <lpage>328</lpage>
          . doi:
          <volume>10</volume>
          .1109/ICSC59802.
          <year>2024</year>
          .
          <volume>00058</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>S.</given-names>
            <surname>Alzahrani</surname>
          </string-name>
          , Metasemap metadata model,
          <year>2025</year>
          . URL: https://github.com/SarahAlzahranitcd/ MetaSEMAP-Metadata.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>