<!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>Towards an Advanced Entity Resolution in Data Lakes</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Lamisse F. BOUABDELLI</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Laboratoire LIAS - ISAE-ENSMA</institution>
          ,
          <addr-line>Téléport 2 - 1 avenue Clément Ader BP 40109, 86961 Chasseneuil</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Research laboratory, Trimane The data intelligence company</institution>
          ,
          <addr-line>102 Terr. Boieldieu, 92800 Puteaux</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <fpage>20</fpage>
      <lpage>23</lpage>
      <abstract>
        <p>Entity Resolution (ER) is a critical challenge for maintaining data quality in data lakes, aiming to identify diferent descriptions that refer to the same real-world entity. We address here the problem of ER in data lakes, where their schema-less architecture and heterogeneous data sources often lead to entity duplication, inconsistency, and ambiguity, causing serious data quality issues. Although ER has been well studied both in academic research and industry, many state-of-the-art ER solutions face significant drawbacks. Existing ER solutions typically compare two entities based on attribute similarity, without taking into account that some attributes contribute more significantly than others in distinguishing entities. In addition, traditional validation methods that rely on human experts are often error-prone, time-consuming, and costly. We propose an eficient ER approach that leverages deep learning, knowledge graph (KG), and large language model (LLM) to automate and enhance entity disambiguation. Furthermore, the matching task incorporates attribute weights, thereby improving accuracy. By integrating LLM for automated validation, this approach significantly reduces the reliance on manual expert verification while maintaining high accuracy.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Data Lakes</kwd>
        <kwd>Data Quality</kwd>
        <kwd>Entity Resolution</kwd>
        <kwd>Entity Matching</kwd>
        <kwd>Machine Learning</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Context and Motivation</title>
      <p>
        The exponential growth in volume, velocity, and variety of data has introduced the concept of Big
Data, which has significantly transformed how organizations store, process, and analyze information.
To manage these large-scale heterogeneous datasets, organizations have adopted data lakes, scalable
storage systems designed to ingest structured, semi-structured, and unstructured data in its raw format
without requiring a predefined schema. This schema-less architecture ofers flexibility and scalability,
making data lakes an attractive solution for organizations seeking to integrate data from diferent
sources[
        <xref ref-type="bibr" rid="ref1 ref2 ref3">1, 2, 3</xref>
        ].
      </p>
      <p>Today, organizations rely on their data for strategic decision making, utilizing advanced analytics,
machine learning, and business intelligence (BI) tools to gain operational eficiency and competitive
advantage. Typically, data from multiple sources are stored in a data lake, then cleaned and transformed
before being ingested into a data warehouse, where they are used for analytics and decision making as
illustrated in Figure 1.</p>
      <p>
        However, Datasets originating from heterogeneous sources inevitably introduce data quality issues,
as they often difer in structure, format, schema and semantics, leading to inconsistencies, duplicate
records, missing attributes, and lack of standardization[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Such issues degrade the accuracy and
reliability of analytical outputs, resulting incorrect decision making.
      </p>
      <p>One of the most critical challenges in data lakes is entity ambiguity, which occurs when multiple
records from diferent datasets and sources represent the same real-world entity but appear in diferent
formats. Conversely, highly similar records may correspond to diferent entities. Figure 2 illustrates
these scenarios:</p>
      <p>• Case (a) shows two records from distinct sources that refer to the same person</p>
      <p>• Case (b) shows two records from distinct sources with quite similar names, identical addresses,
and nearly identical birth dates, but in fact they represent two diferent individuals. Mismatching
them would lead to false positive</p>
      <p>
        In order to improve these issues, organizations require a robust Entity resolution (ER) approach. ER
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] is the process of determining whether two entities refer to the same real-world entity [
        <xref ref-type="bibr" rid="ref6 ref7">6, 7</xref>
        ]. The term
entity refers to a distinct and identifiable unit that represents an object, a person, a place, or a concept
of the real world. An entity has attributes that describe its characteristics. The term resolution is used
because ER is fundamentally a decision-making process to resolve the question: Do the descriptions
refer to the same or diferent entities? [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. ER is also defined as "the process of identifying records
judged to represent the same real-world entity" [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>Since organizations rely on data for important decision-making, the need for a robust ER solution has
never been more critical. In high-stakes domains such as healthcare, finance, and e-commerce, errors in
ER can have severe consequences, from incorrect patient records leading to misdiagnoses, to fraudulent
ifnancial transactions, or misattribute customer data afecting business decisions.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        Entity resolution has been a key area of interest both in academic research [
        <xref ref-type="bibr" rid="ref5 ref7">5, 7</xref>
        ] and industry, evolving
significantly from traditional similarity measures to machine learning techniques that have shown
an improvement in matching performance [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. By the late 2010s, deep learning became a key area of
research in data matching [
        <xref ref-type="bibr" rid="ref10 ref11 ref12">10, 11, 12</xref>
        ]. Other research has studied ER using graph-based methods [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ],
and more recently experimented with LLM [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>
        The industry has proposed many ER solutions using machine learning and artificial intelligence. Among
these solutions, Senzing [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], designed for entity matching, combines ML clustering and AI. Quantexa
[
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] employs ML and AI techniques, ofers entity linkage; however, its reliance on complex graph
structures poses implementation challenges for non-expert users. AWS Glue [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], a cloud-based ER
solution, integrates entity resolution within broader ETL workflows. Its scalability and seamless
integration with AWS services make it a powerful tool. DataWalk [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], on the other hand, is a unified
graph and AI platform for data management, analysis, and investigative intelligence, which includes
entity resolution software.
      </p>
      <p>Despite the advancements ofered by these tools, industrial ER solutions still face key limitations.
A critical drawback is the lack of attribute weighting, where all entity attributes are treated equally
despite varying levels of significance, which can lead to suboptimal matching results. Furthermore, the
validation phase often relies on manual intervention, thereby increasing operational costs and time.
This dependence not only reduces the eficiency of these solutions, but also introduces human error.
Due to these issues, there is a clear need for improvement in industrial ER tools to better address these
challenges. Enhanced attribute weighting mechanisms and the use of reliable automated validation
could significantly refine the accuracy and eficiency of entity resolution in industry.</p>
      <p>
        ER has been a main focus in research for decades and is still receiving attention [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. It started
with domain experts matching entities by hand [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. Now, with advances in technology, machine
learning-based approaches have been introduced, using supervised and unsupervised learning
techniques to improve ER [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Methods such as Support Vector Machines [
        <xref ref-type="bibr" rid="ref19 ref20">19, 20</xref>
        ] classify entity pairs based
on engineered similarity features, while Random Forests [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] employ ensemble learning to improve
classification performance. However, these models require extensive feature engineering and struggle
with unseen entity variations, limiting their adaptability to large and evolving datasets. Transformer
and pre-trained models like BERT [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ] and RoBERTa [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ] revolutionized natural language processing.
Studies have explored entity matching using pre-trained models[
        <xref ref-type="bibr" rid="ref24 ref25">24, 25</xref>
        ]. More recently, deep learning
models have significantly advanced entity resolution by capturing contextual dependencies between
entity attributes. DeepMatcher [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] applies bidirectional LSTM [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ] with attention mechanisms to learn
entity similarity from labeled data, while Ditto [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] uses transformer-based architectures to fine-tune
pre-trained models on ER tasks. Ditto brings some optimizations that require domain knowledge. These
deep learning-based methods are based on text sequences for matching. They use diferent methods
for attribute embedding and attribute similarity representation. Furthermore, HierGAT (Hierarchical
Graph Attention Networks) [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] enhances entity matching by incorporating graph-based
relationships, demonstrating the potential of graph neural networks (GNNs) for ER problems. Despite their
improvements in precision and recall, deep learning-based methods often overlook the importance of
attribute weighting and struggle with explainability, posing challenges for real-world adoption. The
advent of LLM such as Llama and GPT has further pushed the boundaries of ER by enabling zero-shot
and few-shot learning for entity matching tasks [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Although LLM have shown strong performance,
their efectiveness remains highly dependent on domain-specific fine-tuning and prompt engineering,
making them computationally expensive and less adaptable to structured relational datasets. Moreover,
existing LLM-based approaches do not inherently model inter-entity relationships, which limits their
applicability in graph-based ER scenarios.
      </p>
      <p>To clarify, an LLM that performs matching based solely on textual attributes might miss the underlying
relationships between entities. For instance, consider a father and son who share the same last name
and home address. An LLM could mistakenly classify them as the same person due to the high textual
similarity of their attributes. However, the crucial relationship (father–son) indicates they are related
but distinct individuals. This relational nuance cannot be captured by the LLM alone. In contrast, a
knowledge graph can explicitly represent such relationships, enabling the system to recognize them
as separate entities. This example demonstrates why relying exclusively on LLM can be problematic
in graph-based ER settings: LLM lack explicit, structured mechanisms to represent and reason over
inter-entity relationships.</p>
      <p>
        In contrast, research eforts have also explored rule-based methods [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ] that require designing rules
and setting thresholds and crowd-sourcing-based ER methods[
        <xref ref-type="bibr" rid="ref28">28</xref>
        ], which require extensive manual
intervention or rely on human annotators to validate entity matches. As ER continues to evolve, our
research focus on hybrid approaches that combine deep learning, knowledge graphs, and pre-trained
LLM, leveraging the strengths of each paradigm to improve entity resolution across diverse real-world
datasets.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Research Questions</title>
      <p>The growing adoption of data lake within organizations highlights a critical research challenge: how to
identify records originating from diferent sources and datasets that correspond to the same real-world
entity. While existing ER approaches while efective in controlled academic settings, fall short in
enterprise and data lake contexts due to several limitations since they do not take into account the
weight of the attributes, leading to mismatched possibility. In addition, they rely on manual validation,
making the process expensive and time consuming.</p>
      <p>These limitations raise the following research questions:
• RQ1: How can we design a robust ER pipeline tailored for a data lake involving heterogeneous
sources?
• RQ2: How can we efectively incorporate attribute weighting to improve the performance of
entity matching?
• RQ3: How can the ER process be designed to minimize manual intervention?</p>
    </sec>
    <sec id="sec-4">
      <title>4. Research Plan and Methodology</title>
      <p>This section introduces our proposed entity resolution approach. Figure 3 illustrates the pipeline of our
proposed method. This pipeline is designed to operate within the architectural framework shown in
Figure 1, especially between the data lake and the data warehouse.</p>
      <p>
        Our approach is inspired by established techniques in the literature [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], but introduces key adaptations
to improve the entity resolution process. The process consists of four main steps: 1) Pre-processing
ensures data quality by standardizing formats, correcting mistyping errors, handling missing values,
and normalizing variations. 2) Blocking aims to reduce computational complexity by grouping similar
records in the same block to limit entity comparisons to subsets. 3) Matching compares records within
the same block in order to identify records that correspond to the same real-world entity. 4) Validation
is traditionally carried out by domain experts, which is often time-consuming and costly. To address
this, we propose an automated validation mechanism that significantly reduces manual efort.
      </p>
      <p>The following subsections provide a detailed explanation of each phase of the pipeline, including the
specific techniques and methodology used.</p>
      <sec id="sec-4-1">
        <title>4.1. Pre-processing</title>
        <p>
          Pre-processing is a critical step to ensure quality of data, which is essential for entity resolution, but
our contribution does not lie in this phase. In our approach we will adopt state-of-the-art techniques
widely used in the literature [
          <xref ref-type="bibr" rid="ref29 ref7">7, 29</xref>
          ] such as standardization, where data formats such as dates and
addresses are unified, correcting mistyping errors, and identifying missing values. Additionally, linguistic
normalization is applied to unify abbreviations, acronyms, and variations of entity names, plus special
character removal and the elimination of unnecessary punctuations, symbols, and whitespace.
        </p>
        <p>Given that real-world data are often noisy and incomplete, we aim to improve the data quality by
assuring accuracy (ensuring that data correctly reflect real-world entities), consistency (ensuring that
data are harmonized and uniformed across multiple sources), correctness (verify data validity), and
completeness (assessing whether all the essential information is present). Completeness is further
categorized into: total completeness means no missing data, partial completeness some missing data,
but it will not afect the processes and the information remains exploitable, critical completeness where
essential data are missing.</p>
        <p>The goal of pre-processing is to enhance data quality for the next steps. The output of the
preprocessing is clean data, for the purpose of reducing the number of sets for the matching, for this reason
we introduce our next phase.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Blocking</title>
        <p>
          Blocking is an optimization step designed to reduce the number of comparisons between entity pairs,
thus significantly reducing computational costs. Instead of evaluating all possible entity pairs, blocking
groups similar records together in the same block. This ensures that only the most relevant subsets are
considered for a detailed matching [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ].
        </p>
        <p>
          Various blocking techniques have been explored in the literature [
          <xref ref-type="bibr" rid="ref24 ref30 ref6">6, 30, 24</xref>
          ], each with its own
advantages. In our approach, we plan to investigate clustering-based blocking approaches already used
in literature in order to group similar records based on their attributes.
        </p>
        <p>After grouping potentially similar records in blocks and reducing computational complexity as a
result, limiting entity comparisons to subsets that are ready for the next step.</p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Matching</title>
        <p>The matching phase constitutes the most critical step in entity resolution, as it seeks to identify records
that correspond to the same real-world entity, despite variations in their descriptions, a phenomenon
known as synonymy, as illustrated in Figure 2(a). In contrast, it is equally crucial to diferentiate records
that may exhibit similar attributes but actually represent distinct entities, a challenge called homonymy
or entity collision, as shown in Figure 2(b).</p>
        <p>
          Our proposed matching approach incorporates attribute weighting, recognizing that certain attributes
contribute more significantly than others in distinguishing entities. We acknowledge that previous ER
approaches have incorporated attribute importance through weighted similarity. Notably, recent
graphbased models like [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] employ attention mechanisms to identify the most discriminative attributes. To
determine these weights, we investigate two methods: (i) human-based, where domain experts assign
weights for attributes based on their discriminative power, and (ii) machine learning techniques that
automatically infer weights from labeled or partially labeled training data.
        </p>
        <p>To further enhance matching accuracy, our approach combines deep learning techniques using
pretrained language models such as BERT. The similarity between two attribute values is then calculated
using cosine similarity (or alternative distance metrics if appropriate). We plan to combine weighting
mechanisms with deep learning techniques and knowledge graphs that capture the relationships
between entities that are likely to match. This hybrid approach will ultimately improve ER by ensuring
a more context-aware, semantically enriched, and structurally informed matching process, leading to
higher precision and reduced false positives.</p>
        <sec id="sec-4-3-1">
          <title>4.3.1. Problem Formulation</title>
          <p>Figure 4 illustrates a scenario in which existing entity resolution solutions may incorrectly merge two
distinct entities due to high similarity in certain attributes. Specifically, Entity 1 (T3) in the patient table
and Entity 2 (T4 in the citizen table and T5 in the employee table) share common data points, such as
address and name variations, making them appear as potential duplicates. The question arises: How
does our proposed matching approach difer and why is it more efective?</p>
          <p>To formalize the problem, we define the following.</p>
          <p>
            • A dataset consisting of multiple tables  , where each table contains a set of attributes denoted as:
• Attributes, such as in our example name, date of birth, address, and Social Security Number (SSN).
• A weight function  :  → [
            <xref ref-type="bibr" rid="ref1">0, 1</xref>
            ] that assigns a weight to each attribute based on its discriminative
power. For instance, attributes like SSN have a high weight due to their uniqueness:
 = {1, 2, . . . , }.
          </p>
          <p>(SSN) = 0.9,
(name) = 0.7,
(DOB) = 0.5,
(address) = 0.4.</p>
          <p>Matching Computation: Given two records  and  , we calculate a similarity score for each attribute
using deep learning techniques to measure the degree of correspondence between attribute values. This
results in a similarity vector:</p>
          <p>For example:
where each  represents the similarity score for the attribute .</p>
          <p>To compute the final matching score, we apply a weighted sum:</p>
          <p>match(3, 4) = {1, 2, . . . , }.
match(3, 4) = {0.6, 0.8, 1.0, 0.4}.</p>
          <p>(3, 4) = 1 ∑︁ () ·  .</p>
          <p>=1</p>
          <p>
            Alternatively, beyond a simple summation, we plan to investigate the use of the Skyline operator
[
            <xref ref-type="bibr" rid="ref31">31</xref>
            ], which is considered an optimization solution that selects non-dominated matches based on Pareto
optimality.
          </p>
          <p>By incorporating attribute weighting and deep learning-based similarity computation. We aim that
our approach will significantly reduce false positives while improving the precision of entity resolution.</p>
        </sec>
        <sec id="sec-4-3-2">
          <title>4.3.2. Capturing Relationships with Knowledge Graphs</title>
          <p>Figure 4 illustrates an example in which existing entity resolution methods struggle, often erroneously
matching two entities that are, in fact, distinct. However, our method goes beyond similarity matching
by using knowledge graphs to detect relationships between entities rather than incorrectly merging
them.
(1)
(2)
(3)
(4)
(5)</p>
          <p>By integrating knowledge graphs, our approach captures semantic relationships between entities.
In this example, instead of falsely concluding that Entity 1 and Entity 2 are the same person, we
ifnd a related relationships, they are likely father and son. Social Security Numbers (SSN) difer, but
name, address, and other attributes share similarities, which can mislead conventional entity resolution
methods.</p>
          <p>To model this, we define  = {1, 2, . . . , } as the set of entities.  as the set of possible
relationships between entities, where each relationship is defined as a directed edge (,  ) in the
knowledge graph. A similarity function (,  ) that computes the weighted similarity between
records, capturing both direct attribute matches and inferred relationships.</p>
          <p>Using this structure, our method assigns relationship probabilities instead of merely merging entities.
The system recognizes that while Entity 1 and Entity 2 are distinct, they are related, thus preventing
false positives in entity resolution.</p>
          <p>We believe that by combining deep learning techniques for attribute matching with knowledge
graphs for relationship inference, our approach will achieve higher accuracy in distinguishing similar
but distinct entities while assuring the preservation of important relationships rather than erroneous
resolved entities. Plus scalability in handling complexities in real-world data.</p>
          <p>Lastly, after finding entities that match and for the purpose of afirming if the resolved entities are
correctly matched, we present our next step for entity validation.</p>
        </sec>
      </sec>
      <sec id="sec-4-4">
        <title>4.4. Validation</title>
        <p>The validation phase in our pipeline aims to verify that the resolved entities match correctly.
Traditionally, this step relies on domain experts to manually verify. This approach, while reliable, is highly
time-consuming, costly, and prone to human errors, especially when dealing with large-scale datasets.</p>
        <p>To overcome these limitations, we propose an automated validation mechanism using LLM. In
order to check uncertain cases which did not exceed a predefined similarity threshold in the matching
phase without human intervention. Our approach utilizes the reasoning and contextual understanding
capabilities of LLM, allowing them to provide a final layer of confidence in the entity resolution process.</p>
        <p>We are aware that LLM can be used during the matching phase. However, we deliberately restrict their
use to the validation phase because of considerations of cost, scalability, and explainability. Running
an LLM on every candidate pair during matching would be computationally expensive and ineficient,
especially when processing millions of comparisons. In contrast, using LLM only on a reduced subset of
record pairs, those that survived earlier blocking and matching a better balance between accuracy and
performance. This approach allows us to benefit from LLM sophisticated reasoning capabilities.
LLMbased validation step provides a final layer of confidence by validating only the top-ranked candidate
pairs.</p>
        <p>By automating validation, we eliminate the reliance on domain experts for this task, consequently
reducing human efort and operational costs. The approach is highly scalable, capable of eficiently
validating millions of records, which makes it well suited for large-scale entity resolution. Using the
contextual reasoning capabilities of LLM, our method aims to ensure high accuracy by minimizing false
positives and false negatives. Furthermore, the execution speed of our validation mechanism is faster
than manual methods, enabling real-time or near-real-time verification.</p>
        <p>In summary, by integrating deep learning, knowledge graphs, and LLM, our entity resolution approach
aims to ensure a more eficient, scalable, and reliable validation process.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Next Research Step and Expected Final Contribution</title>
      <p>Data quality is a critical challenge in data lakes. Therefore, entity resolution is crucial to enhance data
quality which is essential for making optimal decisions.</p>
      <p>In this paper, we propose a novel entity resolution approach designed to improve data quality,
scalability, and automation in data lakes. Our solution uses deep learning, to improve entity matching,
knowledge graphs, to capture relationships between entities and LLM to reduce human intervention in
the validation phase.</p>
      <p>Our approach presents a potentially efective improvement to existing entity resolution solutions,
but its true performance and eficiency can only be validated through real-world implementation and
experimentation.</p>
      <p>Since our work is currently a theoretical proposition, our next step is to implement this approach and
conduct a comprehensive evaluation against existing solutions. We aim to demonstrate its efectiveness
in the real-world and ultimately contribute to the advancement of entity resolution.</p>
      <p>At this stage, we assume that data sources share an aligned schema, allowing attributes to be directly
compared across sources. In future work, we aim to relax this assumption by explicitly addressing
schema heterogeneity.</p>
      <p>While our approach focuses on the identification of duplicate entities, we acknowledge that the
subsequent step data fusion (merging duplicate records into unified representations) is not addressed
in this paper. Data fusion is a critical and non trivial component of the ER pipeline, and we plan to
investigate scalable and context-aware fusion strategies as part of future work.</p>
      <p>
        However, we note that data fusion has already been explored in previous research eforts [
        <xref ref-type="bibr" rid="ref32 ref33 ref34">32, 33, 34</xref>
        ],
where our team explored merging duplicate records in data lakes using ontology-driven integration.
Building upon such foundations, our future eforts will aim to incorporate a robust, semantically
informed fusion module to complete the ER pipeline.
      </p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgements</title>
      <p>I would like to express my sincere gratitude to my supervisors, Fatma Abdelhedi, Allel Hadjali, and
Slimane Hammoudi, for their guidance and support. Special thanks to Gilles Zurfluh for his valuable
advice and mentorship.</p>
    </sec>
    <sec id="sec-7">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the author used ChatGPT-5 in order to: Grammar and spelling
check.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>P. N.</given-names>
            <surname>Sawadogo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Scholly</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Favre</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Ferey</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Loudcher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Darmont</surname>
          </string-name>
          ,
          <article-title>Metadata systems for data lakes: Models and features</article-title>
          ,
          <source>in: New Trends in Databases and Information Systems: ADBIS 2019 Short Papers</source>
          ,
          <string-name>
            <surname>Workshops</surname>
            <given-names>BBIGAP</given-names>
          </string-name>
          , QAUCA, SemBDM, SIMPDA, M2P, MADEISD, and Doctoral Consortium, Bled, Slovenia, September 8-
          <issue>11</issue>
          ,
          <year>2019</year>
          , Proceedings 23, Springer,
          <year>2019</year>
          , pp.
          <fpage>440</fpage>
          -
          <lpage>451</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>F.</given-names>
            <surname>Ravat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <article-title>Data lakes: Trends and perspectives</article-title>
          ,
          <source>in: International Conference on Database and Expert Systems Applications</source>
          , Springer,
          <year>2019</year>
          , pp.
          <fpage>304</fpage>
          -
          <lpage>313</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>P.</given-names>
            <surname>Sawadogo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Darmont</surname>
          </string-name>
          ,
          <article-title>On data lake architectures and metadata management</article-title>
          ,
          <source>Journal of Intelligent Information Systems</source>
          <volume>56</volume>
          (
          <year>2021</year>
          )
          <fpage>97</fpage>
          -
          <lpage>120</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M. H.</given-names>
            <surname>Moslemi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Mousavi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Behkamal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Milani</surname>
          </string-name>
          ,
          <article-title>Heterogeneity in entity matching: A survey and experimental analysis</article-title>
          ,
          <source>arXiv preprint arXiv:2508.08076</source>
          (
          <year>2025</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>N.</given-names>
            <surname>Barlaug</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Gulla</surname>
          </string-name>
          ,
          <article-title>Neural networks for entity matching: A survey, ACM Transactions on Knowledge Discovery from Data (TKDD) 15 (</article-title>
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>37</lpage>
          . doi:
          <volume>10</volume>
          .1145/3442200.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>V.</given-names>
            <surname>Christophides</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Efthymiou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Palpanas</surname>
          </string-name>
          , G. Papadakis,
          <string-name>
            <given-names>K.</given-names>
            <surname>Stefanidis</surname>
          </string-name>
          ,
          <article-title>An overview of end-to-end entity resolution for big data</article-title>
          ,
          <source>ACM Computing Surveys (CSUR) 53</source>
          (
          <year>2020</year>
          )
          <fpage>1</fpage>
          -
          <lpage>42</lpage>
          . doi:
          <volume>10</volume>
          .1145/ 3418896.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>P.</given-names>
            <surname>Christen</surname>
          </string-name>
          , Data Matching,
          <source>Springer: Data-centric systems and applications</source>
          ,
          <year>2012</year>
          . doi:
          <volume>10</volume>
          .1007/ 978-3-
          <fpage>642</fpage>
          -31164-2.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>J.</given-names>
            <surname>Talburt</surname>
          </string-name>
          , Entity Resolution and Information Quality, Elsevier,
          <year>2011</year>
          . doi:
          <volume>10</volume>
          .1016/ C2009-0-63396-1.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>O.</given-names>
            <surname>Benjelloun</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Garcia-Molina</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Gong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Kawai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T. E.</given-names>
            <surname>Larson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Menestrina</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Thavisomboon</surname>
          </string-name>
          ,
          <article-title>D-swoosh: A family of algorithms for generic, distributed entity resolution</article-title>
          ,
          <source>in: 27th International Conference on Distributed Computing Systems (ICDCS'07)</source>
          , IEEE,
          <year>2007</year>
          , pp.
          <fpage>37</fpage>
          -
          <lpage>37</lpage>
          . doi:
          <volume>10</volume>
          .1109/ ICDCS.
          <year>2007</year>
          .
          <volume>96</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>R.</given-names>
            <surname>Peeters</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Steiner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Bizer</surname>
          </string-name>
          ,
          <article-title>Entity matching using large language models</article-title>
          ,
          <source>arXiv preprint arXiv:2310.11244</source>
          (
          <year>2024</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>S.</given-names>
            <surname>Mudgal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Rekatsinas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Doan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Park</surname>
          </string-name>
          , G. Krishnan,
          <string-name>
            <given-names>R.</given-names>
            <surname>Deep</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Arcaute</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Raghavendra</surname>
          </string-name>
          ,
          <article-title>Deep learning for entity matching: A design space exploration</article-title>
          ,
          <source>in: Proceedings of the 2018 international conference on management of data</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>19</fpage>
          -
          <lpage>34</lpage>
          . doi:
          <volume>10</volume>
          .1145/3183713.3196926.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Suhara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Doan</surname>
          </string-name>
          , W.-C. Tan,
          <article-title>Deep entity matching with pre-trained language models</article-title>
          ,
          <source>Proceedings of the VLDB Endowment</source>
          <volume>14</volume>
          (
          <year>2020</year>
          )
          <fpage>50</fpage>
          -
          <lpage>60</lpage>
          . doi:
          <volume>10</volume>
          .14778/3421424.3421431.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>D.</given-names>
            <surname>Yao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Gu</surname>
          </string-name>
          , G. Cong,
          <string-name>
            <given-names>H.</given-names>
            <surname>Jin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Lv</surname>
          </string-name>
          ,
          <article-title>Entity resolution with hierarchical graph attention networks</article-title>
          ,
          <source>in: Proceedings of the 2022 International Conference on Management of Data</source>
          ,
          <year>2022</year>
          , pp.
          <fpage>429</fpage>
          -
          <lpage>442</lpage>
          . doi:
          <volume>10</volume>
          .1145/3514221.3517872.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>I. Senzing</surname>
          </string-name>
          , Senzing - entity resolution software, https://senzing.com/,
          <year>2025</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Quantexa</surname>
          </string-name>
          , Quantexa, https://www.quantexa.com/fr/,
          <year>2025</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <surname>AWS</surname>
          </string-name>
          ,
          <string-name>
            <surname>Aws</surname>
            <given-names>glue</given-names>
          </string-name>
          , https://aws.amazon.com/fr/glue/,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>Datawalk</surname>
          </string-name>
          ,
          <article-title>Data walk entity resolution</article-title>
          , https://datawalk.com/solutions/entity-resolution/,
          <year>2025</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>I. P.</given-names>
            <surname>Fellegi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. B.</given-names>
            <surname>Sunter</surname>
          </string-name>
          ,
          <article-title>A theory for record linkage</article-title>
          ,
          <source>Journal of the American statistical association 64</source>
          (
          <year>1969</year>
          )
          <fpage>1183</fpage>
          -
          <lpage>1210</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>C.</given-names>
            <surname>Cortes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Vapnik</surname>
          </string-name>
          ,
          <article-title>Support-vector networks</article-title>
          ,
          <source>Machine learning 20</source>
          (
          <year>1995</year>
          )
          <fpage>273</fpage>
          -
          <lpage>297</lpage>
          . doi:
          <volume>10</volume>
          . 1007/BF00994018.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>M.</given-names>
            <surname>Bilenko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Mooney</surname>
          </string-name>
          ,
          <article-title>Adaptive duplicate detection using learnable string similarity measures</article-title>
          ,
          <source>in: Proceedings of the ninth ACM SIGKDD international conference on Knowledge discovery and data mining</source>
          ,
          <year>2003</year>
          , pp.
          <fpage>39</fpage>
          -
          <lpage>48</lpage>
          . doi:
          <volume>10</volume>
          .1145/956750.956759.
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>L.</given-names>
            <surname>Breiman</surname>
          </string-name>
          , Random forests,
          <source>Machine learning 45</source>
          (
          <year>2001</year>
          )
          <fpage>5</fpage>
          -
          <lpage>32</lpage>
          . doi:
          <volume>10</volume>
          .1023/A:
          <fpage>1010933404324</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>J.</given-names>
            <surname>Devlin</surname>
          </string-name>
          , M.-
          <string-name>
            <given-names>W.</given-names>
            <surname>Chang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Toutanova</surname>
          </string-name>
          , Bert:
          <article-title>Pre-training of deep bidirectional transformers for language understanding</article-title>
          , arXiv preprint arXiv:
          <year>1810</year>
          .
          <volume>04805</volume>
          (
          <year>2018</year>
          )
          <article-title>15</article-title>
          . doi:
          <volume>10</volume>
          .48550/arXiv.
          <year>1810</year>
          .
          <volume>04805</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ott</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Goyal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Du</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Joshi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Levy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lewis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Zettlemoyer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Stoyanov</surname>
          </string-name>
          ,
          <article-title>Roberta: A robustly optimized bert pretraining approach</article-title>
          , arXiv preprint arXiv:
          <year>1907</year>
          .
          <volume>11692</volume>
          (
          <year>2019</year>
          ). doi:
          <volume>10</volume>
          .48550/arXiv.
          <year>1907</year>
          .
          <volume>11692</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>M.</given-names>
            <surname>Paganelli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Tiano</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Guerra</surname>
          </string-name>
          ,
          <article-title>A multi-facet analysis of bert-based entity matching models</article-title>
          ,
          <source>The VLDB Journal</source>
          <volume>33</volume>
          (
          <year>2024</year>
          )
          <fpage>1039</fpage>
          -
          <lpage>1064</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Suhara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Hirota</surname>
          </string-name>
          , W.-c. Tan,
          <article-title>Deep entity matching: Challenges and opportunities</article-title>
          ,
          <source>Journal of Data and Information Quality (JDIQ) 13</source>
          (
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>17</lpage>
          . doi:
          <volume>10</volume>
          .1145/ 3431816.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>S.</given-names>
            <surname>Hochreiter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Schmidhuber</surname>
          </string-name>
          ,
          <article-title>Long short-term memory</article-title>
          ,
          <source>Neural computation 9</source>
          (
          <year>1997</year>
          )
          <fpage>1735</fpage>
          -
          <lpage>1780</lpage>
          . doi:
          <volume>10</volume>
          .1162/neco.
          <year>1997</year>
          .
          <volume>9</volume>
          .8.1735.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>R.</given-names>
            <surname>Singh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Meduri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Elmagarmid</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Madden</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Papotti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-A.</given-names>
            <surname>Quiané-Ruiz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Solar-Lezama</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Tang</surname>
          </string-name>
          ,
          <article-title>Generating concise entity matching rules</article-title>
          ,
          <source>in: Proceedings of the 2017 ACM International Conference on Management of Data</source>
          ,
          <year>2017</year>
          , pp.
          <fpage>1635</fpage>
          -
          <lpage>1638</lpage>
          . doi:
          <volume>10</volume>
          .1145/3035918.3058739.
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>J.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Kraska</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. J.</given-names>
            <surname>Franklin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Feng</surname>
          </string-name>
          , Crowder: Crowdsourcing entity resolution,
          <source>arXiv preprint arXiv:1208</source>
          .
          <year>1927</year>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>S.</given-names>
            <surname>Vijayarani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. J.</given-names>
            <surname>Ilamathi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Nithya</surname>
          </string-name>
          , et al.,
          <article-title>Preprocessing techniques for text mining-an overview</article-title>
          ,
          <source>International Journal of Computer Science &amp; Communication Networks</source>
          <volume>5</volume>
          (
          <year>2015</year>
          )
          <fpage>7</fpage>
          -
          <lpage>16</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>D.</given-names>
            <surname>Skoutas</surname>
          </string-name>
          , E. Thanos,
          <string-name>
            <given-names>T.</given-names>
            <surname>Palpanas</surname>
          </string-name>
          ,
          <article-title>A survey of blocking and filtering techniques for entity resolution</article-title>
          , arXiv preprint arXiv:
          <year>1905</year>
          .
          <volume>06167</volume>
          (
          <year>2019</year>
          ). doi:
          <volume>10</volume>
          .48550/arXiv.
          <year>1905</year>
          .
          <volume>06167</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>S.</given-names>
            <surname>Borzsony</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Kossmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Stocker</surname>
          </string-name>
          ,
          <article-title>The skyline operator</article-title>
          ,
          <source>in: Proceedings 17th international conference on data engineering</source>
          , IEEE,
          <year>2001</year>
          , pp.
          <fpage>421</fpage>
          -
          <lpage>430</lpage>
          . doi:
          <volume>10</volume>
          .1109/ICDE.
          <year>2001</year>
          .
          <volume>914855</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <given-names>F.</given-names>
            <surname>Abdelhedi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Jemmali</surname>
          </string-name>
          ,
          <string-name>
            <surname>G.</surname>
          </string-name>
          <article-title>Zurfluh, Data Ingestion from a Data Lake: The Case of Documentoriented NoSQL Databases</article-title>
          , in: J.
          <string-name>
            <surname>Filipe</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Smialek</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Brodsky</surname>
          </string-name>
          , S. Hammoudi (Eds.),
          <source>Proceedings of the 24th International Conference on Enterprise Information Systems - ICEIS 2022 ; ISBN 978-989-758-569-2 ; ISSN 2184-4992</source>
          , volume
          <volume>1</volume>
          : ICEIS, SCITEPRESS : Science and
          <string-name>
            <given-names>Technology</given-names>
            <surname>Publications</surname>
          </string-name>
          , Online Streaming, France,
          <year>2022</year>
          , pp.
          <fpage>226</fpage>
          -
          <lpage>233</lpage>
          . URL: https://hal.science/hal-03758340. doi:
          <volume>10</volume>
          .5220/0011068300003179.
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>F.</given-names>
            <surname>Abdelhedi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Jemmali</surname>
          </string-name>
          , G. Zurfluh,
          <article-title>DLToDW: Transferring Relational and NoSQL Databases from a Data Lake</article-title>
          ,
          <source>SN Computer Science</source>
          <volume>3</volume>
          (
          <year>2022</year>
          )
          <article-title>article 381</article-title>
          . URL: https://hal.science/hal-03758354. doi:
          <volume>10</volume>
          .1007/s42979-022-01287-7.
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          [34]
          <string-name>
            <given-names>F.</given-names>
            <surname>Abdelhedi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Jemmali</surname>
          </string-name>
          , G. Zurfluh,
          <article-title>Ingestion of a data lake into a nosql data warehouse: The case of relational databases</article-title>
          .,
          <source>in: KMIS</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>64</fpage>
          -
          <lpage>72</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>