<!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>
      <journal-title-group>
        <journal-title>March</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>End-to-End Deep Entity Resolution without Labelled Instances</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Franziska Neuhof</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marco Fisichella</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>George Papadakis</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>L3S Research Center</institution>
          ,
          <addr-line>Hannover</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>National and Kapodistrian University of Athens</institution>
          ,
          <addr-line>Athens</addr-line>
          ,
          <country country="GR">Greece</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2026</year>
      </pub-date>
      <volume>24</volume>
      <issue>2026</issue>
      <fpage>0000</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>Entity Resolution (ER) is a critical data integration task that is addressed through the Filtering-Verification framework. Filtering leverages unsupervised techniques for reducing the computational cost to the most similar candidate pairs, whereas Verification typically uses supervised learning techniques to distinguish between matching and non-matching pairs of entities. The state-of-the-art Verification methods leverage Deep Learning in combination with language models. Despite their high accuracy, their applicability is limited, due to their requirement for a large number of labelled instances from the dataset at hand. To address this issue, we propose a novel methodology for end-to-end Deep ER that waives the need for labelled instances. In essence, it associates the pair of data sources at hand &lt; 1, 2 &gt; with the another pair of data sources of known groundtruth, &lt; 1, 2 &gt;, whose similarity distributions after Filtering are very close. The Verification method is then trained on the candidate pairs of &lt; 1, 2 &gt; and applied to the candidate pairs of &lt; 1, 2 &gt;, linking their records without any labelled instances. Through a thorough experimental study that involves six datasets from two diferent domains, we demonstrate the high efectiveness of our approach, which outperforms established methods that require no labelled instances, while approximating the performance of the state-of-the-art Verification algorithms.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Entity Resolution</kwd>
        <kwd>Entity Matching</kwd>
        <kwd>Deep Learning</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>To address these challenges, we propose an end-to-end ER pipeline that integrates Filtering and
Verification, which applies both Matching and Clustering. This pipeline is designed to be adaptable: The
Matching algorithm can be trained on datasets with ground truth and then applied to diferent datasets,
while Filtering and Clustering can be applied using default values, requiring no labelled instances. This
allows the full pipeline to generalise efectively to datasets without labelled data, providing a robust
foundation for entity resolution tasks across diverse datasets.</p>
      <p>In this work, we focus on finding the overlap between two datasets, which are duplicate free. As shown
in Figure 1, our approach identifies the pair of datasets from a set of dataset pairs &lt; ,1, ,2 &gt;∈ D
with known ground truth which is most similar to the input pair of datasets without labelled instances,
&lt; 1, 2 &gt;. We denote the dataset pair most similar to &lt; 1, 2 &gt; by &lt; ′1, ′2 &gt;. This is achieved
by comparing the similarity distributions after Filtering. The set of candidate pairs from &lt; ′1, ′2 &gt;
is then used to train the Matching algorithm, which is subsequently applied to the candidate pairs of
&lt; 1, 2 &gt;. Finally, we employ clustering algorithms to refine the pairs generated by the Matching
algorithm. Our approach aims to enhance the scalability and applicability of ER systems, making
them more versatile and eficient in real-world applications. Through an extensive experimental study
involving six datasets from two distinct domains, we demonstrate the high efectiveness of our approach.
It approximates the performance of state-of-the-art Verification algorithms, which require labelled
training instances, while outperforming established methods that require no labelled instances.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Problem Definition</title>
      <p>We define as an entity profile with id  or just entity  as a uniquely identified set of name-value
pairs:  =&lt; , {(name, value)} &gt;. Note that this plain data model accommodates data formats of any
structuredness, from structured records (in relational databases or CSV files) to semi-structured entity
descriptions (in RDF) and to free-text. A set of entity profiles of this form is called data source.</p>
      <p>ER typically comes in one of two forms: (i) Record Linkage, also known as Clean-Clean ER, receives as
input two individually duplicate-free data sources, 1 and 2, which are overlapping, i.e., sharing some
of their entity profiles. (ii) Deduplication, also known as Dirty ER, receives as input a single dataset, ,
with duplicates in itself. In both cases, the output comprises the matching entity profiles.</p>
      <p>In this context, we formally define the task we are tackling in this work as follows: Given two data
sources &lt; 1, 2 &gt;, which lack labelled entity pairs, along with a set of data source pairs D, each with a
known groundtruth, detect the matching entity profiles in &lt; 1, 2 &gt; by leveraging the training instances
provided by D so as to maximize the efectiveness in terms of recall, precision and F-Measure.</p>
      <p>This definition applies to Record Linkage, but can be easily extended to Deduplication. It focuses on
end-to-end ER pipelines that perform both Filtering and Verification, as shown in Figure 1. Filtering
receives two datasets, 1 and 2, and outputs the candidate pairs . Verification involves two steps: (i)
Matching estimates the matching likelihood between the entities of each candidate pair. (ii) Clustering
partitions the similarity graph into the set of matching entities, resolving the conflicts that may arise
after Matching (e.g., an entity from 1 is matched with two or more entities from 2).</p>
    </sec>
    <sec id="sec-3">
      <title>3. Approach</title>
      <p>Our goal is to apply end-to-end ER pipelines that combine the state-of-the-art DL-based matching
algorithms with an unsupervised state-of-the-art filtering method. We can waive the need to train
the matchers on a large set of labelled instances by using other datasets with known-groundtruth as
training sets. Based on Problem 1, which dictates that the input comprises a pair of data sources with no
labelled instances, &lt; 1, 2 &gt;, along with a set of data source pairs D, each with a known groundtruth,
our solution consists of the following steps:</p>
      <p>1) We apply a predetermined Filtering method with specific parameter configuration to each labelled
data source pair &lt; ,1, ,2 &gt;∈ D, yielding a set of candidate pairs  .</p>
      <p>2) For each labelled data source pair &lt; ,1, ,2 &gt;∈ D, we convert the entities  and  in each
candidate pair , ∈  into the embedding vectors  and  using a pre-trained SBERT model.
Then, we compute the cosine similarity of the resulting vectors, i.e., (,  ), yielding a similarity
distribution  per data source pair &lt; ,1, ,2 &gt;.</p>
      <p>3) We apply the same filtering method with the same configuration to the unlabelled data source pair,
&lt; 1, 2 &gt;, yielding the set of candidate pairs .</p>
      <p>4) We estimate the similarity distribution , by converting all pairs of entities in  into pairs of
SBERT embedding vectors and computing their cosine similarity.</p>
      <p>5) Using KL-divergence, we estimate the similarity distribution ′ of the data source pairs in D that
is closer to . The selected data source pair is denoted by ′.</p>
      <p>6) We train the selected matching algorithm on all candidate pairs extracted from ′, ′ , using the
respective groundtruth for assigning their labels.</p>
      <p>7) We apply the trained matching algorithm on the candidate pairs of the given unlabelled data source
pair, . As a result, each candidate pair in  is associated with a matching probability, yielding a
weighted undirected similarity graph .</p>
      <p>8) We remove any conflicts from the matching outcomes, by applying a clustering algorithm to the
similarity graph  to produce the final output.</p>
      <p>To put this methodology into practice, we need to specify the algorithms that are used for Filtering,
Matching and Clustering.</p>
      <p>
        Starting with the Filtering algorithm, we selected kNN Join, which converts each entity into a sparse
-gram vector and then identifies its  nearest neighbors using Cosine, Dice or Jaccard similarity.
kNN Join consistently achieves very high efectiveness, while being easily configured [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Its default
configuration actually exhibits the highest performance across all methods considered in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Another
advantage is its schema-agnostic functionality, which considers all attribute values, regardless of the
associated attribute names. This way, it minimizes the need for human intervention, while increasing
the robustness to schema heterogeneity and noise in attribute names and values.
      </p>
      <p>
        For Matching, there is no clear winner among DITTO [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ], EMTransformer [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] and GNEM [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
We combine our methodology with all three of them in order to experimentally identify the best choice.
      </p>
      <p>
        Finally, for Clustering, the best balance between efectiveness and time eficiency is achieved by
UMC, which excels in balanced datasets, where there is a relatively equal number of duplicates in 1
and 2, and EC, which excels in all other types of datasets [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
3.1. Fine-tuning Configuration Parameters
The performance of the methods comprising our approach is significantly afected by their configuration
parameters [
        <xref ref-type="bibr" rid="ref1 ref6 ref7">1, 6, 7</xref>
        ]. Hence, we consider two types of parameter configurations: (i) The fine-tuned ones,
which correspond to the ideal case, where every method in the end-to-end ER pipeline has the optimal
hyperparameter values for the data at hand. These values are determined through grid search. (ii) The
default ones, which correspond to the realistic case, where the same hyperparameter values are used in
all datasets. These values have been determined through extensive experimental analysis.
      </p>
      <p>
        In this context, it is worth delving into the exact configuration parameters of each considered
algorithm. kNN-Join is configured by: (i) Prep, a binary parameter that specifies whether pre-processing
(i.e., stemming and stop-word removal) is applied or not, (ii) Indexing, a binary parameter that specifies
whether the smallest data source is used for indexing and the largest one for querying or vice versa,
(iii) Q, a numeric parameter  that determines the size of the q-gram, with  ∈ [
        <xref ref-type="bibr" rid="ref2 ref5">2, 5</xref>
        ], (iv) Multiset, a
binary parameter that specifies whether we consider a set of q-grams (ignoring duplicate ones) or a
multi-set (treating each q-gram as a diferent signature), (v) Similarity, a categorical parameter that
specifies the similarity function used to estimate how similar two sparse entity vectors are (i.e., Dice,
Jaccard or cosine), and (vi) K, numeric parameter  that specifies the number of candidates per query
entity, with  ∈ [
        <xref ref-type="bibr" rid="ref1 ref10">1, 10</xref>
        ]. The following default configuration achieves consistently high performance
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]: Prep=true, Indexing= largest, k=5, Q=5, Similarity=cosine, Multiset=true.
      </p>
      <p>For the Matching algorithms, the number of epochs is the only hyperparameter that we fine-tune,
with a maximum of 40 epochs. Preliminary experiments indicated that a suitable default value is 25
epochs – in many cases, the considered matching algorithms achieved their best performance with
lower epochs, while a few reached their best performance after more than 30 epochs. For all other
hyperparameters, we use default values determined by their open-source implementation.</p>
      <p>For the Clustering algorithms, the only configuration parameter is the similarity threshold,  ∈ [0, 1),
which prunes the edges with a similarity score lower than . The default value of  has been set to 0.5,
as a matching probability lower than 0.5 indicates pairs of entities that most likely are not matching.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Experimental Analysis</title>
      <p>
        Experimental Setup. The complete code (in Python) and data are available on GitHub1. We selected
six commonly used datasets [
        <xref ref-type="bibr" rid="ref3 ref4 ref6 ref8 ref9">6, 3, 4, 8, 9</xref>
        ], from two distinct domains: 1, 2, and 6 originate from
the product domain, while 3, 4 and 5 pertain to TV-Shows. The statistics of these datasets are
reported in Table 1 in increasing computational cost for the brute-force approach (|1 × 2|). The
experiments were conducted on a GPU cluster equipped with NVIDIA A100 GPUs with a memory of
40GB along with AMD EPYC CPUs. To ensure comparability, the experiments were restricted to using
1 GPU (if necessary) and 8 CPUs. Regarding the baseline methods, we use two kinds: (i) Approches
      </p>
      <p>
        DITTO
EMTransformer
GNEM
ZeroER
DADER
Unicorn
DITTO
EMTransformer
GNEM
ZeroER
DADER
Unicorn
DITTO
EMTransformer
GNEM
ZeroER
DADER
Unicorn
DITTO
EMTransformer
GNEM
ZeroER
DADER
Unicorn
DITTO
EMTransformer
GNEM
ZeroER
DADER
Unicorn
DITTO
EMTransformer
GNEM
ZeroER
DADER
Unicorn
(f) Performance of the end-to-end pipelines on 6.
specifically designed to be applied to datasets without labelled instances, namely ZeroER [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], Unicorn
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and DADER [
        <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
        ], and (ii) Traditional supervised learning matching algorithms, namely DITTO,
EMTransformer and GNEM, in combination with our Filtering approach. These settings correspond
to the ideal case, where the dataset at hand had labelled all candidate pairs generated by Filtering. In
this case, we use 60% of the candidate pairs for training, 20% for validation and the remaining 20% for
testing. Our methodology trains DITTO, EMTransformer and GNEM on the selected labelled dataset
′, using 80% of the labelled candidate pairs as training data and the remaining 20% as validation data.
Training is run for 40 epochs. Under the fine-tuned configuration settings, the learned model at the
epoch with the highest validation F1 is applied to all candidate pairs of the unlabelled target dataset .
Filtering performance. The performance of kNN-Join, is reported in Table 2 along with its fine-tuned
and default parameter configurations. For the fine-tuned settings, we consider the configuration that
was determined in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] through grid search with the following optimization goal: maximize precision
for recall at least 0.90; otherwise maximize recall. In this way, Filtering ensures suficiently high levels
of recall for Verification, while minimizing the false positives, i.e., the non-matching candidate pairs.
We observe that the overall Filtering time is quite low in all cases, as all datasets are processed in at
most 2.5 minutes. Most importantly, the selected Filtering approach provides suficiently high recall in
almost all cases, at the cost of low precision. These settings call for a Verification method, which should
maintain recall to very high levels, while raising precision by several times.
      </p>
      <p>Research Question 1: How does our methodology compare to ZeroER, DADER and Unicorn, the main
end-to-end ER pipelines that also require no labelled instances? Looking into Table 3, we observe that
our methodology ofers significant advantages over the other state-of-the-art approaches that require
no labelled datasets. Combined with GNEM, it outperforms ZeroER, DADER and Unicorn, on average,
provided that there is suficient GPU RAM to support labelled datasets with large sets of candidate
pairs. As an alternative, EMTransformer trades higher scalability and robustness for slightly lower
efectiveness – only Unicorn achieves higher F-Measure, on average, because it requires a large amount
of training data to achieve this performance on unlabelled datasets.</p>
      <p>Research Question 2: How does our methodology compare to the traditional DL-based settings, which
require a large dataset of labelled instances of the dataset at hand? We compare the performance on
the “Labelled Dataset” columns of Table 3 with the adjacent ones of the “Same Dataset”. DITTO’s
efectiveness raises significantly when trained on instances from the same dataset: it underperforms
by 19% and 31% under the fine-tuned and the default configurations, respectively, regardless of the
clustering algorithm. This applies to all datasets except 6.</p>
      <p>EMTransformer also underperforms the traditional settings in all cases, without any single exception
(unlike DITTO). In half the datasets, though, its performance is very close to the traditional settings
under the fine-tuned settings. The diference between the two approaches is &lt;4%, &lt;3% and &lt;6% in 3,
4 and 6, respectively, for both clustering algorithms. As a result, EMTransformer lies much closer
to the traditional approach than DITTO.</p>
      <p>The best performance, by far, is exhibited by GNEM. Under the fine-tuned configurations, it is very
close to the traditional settings in 3 and 4, underperforming by just &lt;4% and &lt;1%, respectively,
regardless of the clustering algorithm. In 6, its performance even outperforms the traditional settings
by 2% and 5% for UMC and EC, respectively. Only in 5, it underperforms the traditional settings by
&gt;15%. However, it sufers from instability, given that it does not scale to 1 and 2. This applies to
the default configurations, too, where it does not scale in 3 and 4.</p>
      <p>Overall, GNEM constitutes the most efective choice for our approach in case there are no hardware
limitations, exhibiting a performance very close or even better than the traditional settings. Te most
robust solution for our approach is EMTransformer, at the cost of a slightly lower efectiveness.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusions</title>
      <p>We presented a novel methodology for applying deep ER end-to-end pipelines without requiring
any labelled instances from the input data sources, 1 and 2. It leverages the Filtering-Verification
framework, using a high-end unsupervised technique for the former step. The same Filtering technique
is applied to a set of labelled dataset pairs D, generating candidate pairs with high recall and low
precision. The candidate pairs of &lt; 1, 2 &gt; are compared with those of all dataset pairs in D and the
one with the closest similarity distribution is used as a training set for the DL-based matching algorithm.
The resulting trained matcher together with a clustering algorithm form the Verification step. Our
experimental analysis demonstrates the high efectiveness of our methodology, which outperforms most
relevant techniques from the literature. The best results are achieved when using GNEM as the matching
algorithm, with EMTransformer following in close distance. In the future, we plan to investigate ways
of improving the selection of the labelled dataset and perhaps of the instances extracted from it.
Acknowledgements. This work was partially funded by the EU Horizon project RECITALS (Grant
Agreement 101168490).</p>
    </sec>
    <sec id="sec-6">
      <title>Declaration on Generative AI</title>
      <p>The authors have not employed any Generative AI tools.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>F.</given-names>
            <surname>Neuhof</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Fisichella</surname>
          </string-name>
          , G. Papadakis,
          <string-name>
            <given-names>K.</given-names>
            <surname>Nikoletos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Augsten</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Nejdl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Koubarakis</surname>
          </string-name>
          ,
          <article-title>Open benchmark for filtering techniques in entity resolution</article-title>
          ,
          <source>VLDB J</source>
          .
          <volume>33</volume>
          (
          <year>2024</year>
          )
          <fpage>1671</fpage>
          -
          <lpage>1696</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <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>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <article-title>Deep entity matching: Challenges and opportunities</article-title>
          ,
          <source>ACM J. Data Inf. Qual</source>
          .
          <volume>13</volume>
          (
          <year>2021</year>
          ) 1:
          <fpage>1</fpage>
          -
          <lpage>1</lpage>
          :
          <fpage>17</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <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>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <article-title>Deep entity matching with pre-trained language models</article-title>
          ,
          <source>Proc. VLDB Endow</source>
          .
          <volume>14</volume>
          (
          <year>2020</year>
          )
          <fpage>50</fpage>
          -
          <lpage>60</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>U.</given-names>
            <surname>Brunner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Stockinger</surname>
          </string-name>
          ,
          <article-title>Entity matching with transformer architectures - A step forward in data integration</article-title>
          , in: A.
          <string-name>
            <surname>Bonifati</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Zhou</surname>
            ,
            <given-names>M. A. V.</given-names>
          </string-name>
          <string-name>
            <surname>Salles</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Böhm</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Olteanu</surname>
            ,
            <given-names>G. H. L.</given-names>
          </string-name>
          <string-name>
            <surname>Fletcher</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Khan</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          Yang (Eds.),
          <source>Proceedings of the 23rd International Conference on Extending Database Technology, EDBT</source>
          <year>2020</year>
          , Copenhagen, Denmark, March 30 - April 02,
          <year>2020</year>
          , OpenProceedings.org,
          <year>2020</year>
          , pp.
          <fpage>463</fpage>
          -
          <lpage>473</lpage>
          . URL: https://doi.org/10.5441/002/edbt.
          <year>2020</year>
          .
          <volume>58</volume>
          . doi:
          <volume>10</volume>
          .5441/002/EDBT.
          <year>2020</year>
          .
          <volume>58</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>R.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Shen</surname>
          </string-name>
          ,
          <string-name>
            <surname>D. Zhang,</surname>
          </string-name>
          <article-title>GNEM: A generic one-to-set neural entity matching framework</article-title>
          ,
          <source>in: WWW</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>1686</fpage>
          -
          <lpage>1694</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>G.</given-names>
            <surname>Papadakis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Kirielle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Christen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Palpanas</surname>
          </string-name>
          ,
          <article-title>A critical re-evaluation of record linkage benchmarks for learning-based matching algorithms</article-title>
          ,
          <source>ICDE</source>
          (
          <year>2024</year>
          )
          <fpage>3435</fpage>
          -
          <lpage>3448</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>G.</given-names>
            <surname>Papadakis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Efthymiou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Thanos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Hassanzadeh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Christen</surname>
          </string-name>
          ,
          <article-title>An analysis of one-to-one matching algorithms for entity resolution</article-title>
          ,
          <source>VLDB J</source>
          .
          <volume>32</volume>
          (
          <year>2023</year>
          )
          <fpage>1369</fpage>
          -
          <lpage>1400</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>H.</given-names>
            <surname>Köpcke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Thor</surname>
          </string-name>
          , E. Rahm,
          <article-title>Evaluation of entity resolution approaches on real-world match problems</article-title>
          ,
          <source>Proc. VLDB Endow</source>
          .
          <volume>3</volume>
          (
          <year>2010</year>
          )
          <fpage>484</fpage>
          -
          <lpage>493</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>D.</given-names>
            <surname>Obraczka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Schuchart</surname>
          </string-name>
          , E. Rahm,
          <article-title>Embedding-assisted entity resolution for knowledge graphs</article-title>
          ,
          <source>in: (ESWC</source>
          , volume
          <volume>2873</volume>
          <source>of CEUR Workshop Proceedings</source>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>R.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Chaba</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Sawlani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Chu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Thirumuruganathan</surname>
          </string-name>
          , Zeroer:
          <article-title>Entity resolution using zero labeled examples</article-title>
          ,
          <source>in: Proceedings of the 2020 ACM SIGMOD International Conference on Management of Data</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>1149</fpage>
          -
          <lpage>1164</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>J.</given-names>
            <surname>Tu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Fan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Tang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Du</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Jia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Gao</surname>
          </string-name>
          ,
          <article-title>Unicorn: A unified multi-tasking model for supporting matching tasks in data integration 1 (</article-title>
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>J.</given-names>
            <surname>Tu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Fan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Tang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Chai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Fan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Du</surname>
          </string-name>
          ,
          <article-title>Domain adaptation for deep entity resolution</article-title>
          ,
          <source>in: Proceedings of the 2022 International Conference on Management of Data, SIGMOD '22</source>
          ,
          <string-name>
            <surname>Association</surname>
          </string-name>
          for Computing Machinery, New York, NY, USA,
          <year>2022</year>
          , p.
          <fpage>443</fpage>
          -
          <lpage>457</lpage>
          . URL: https://doi.org/10.1145/3514221.3517870. doi:
          <volume>10</volume>
          .1145/3514221.3517870.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>J.</given-names>
            <surname>Tu</surname>
          </string-name>
          , X. Han,
          <string-name>
            <surname>J</surname>
          </string-name>
          . Fan,
          <string-name>
            <given-names>N.</given-names>
            <surname>Tang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Chai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <surname>X.</surname>
          </string-name>
          <article-title>Du, DADER: hands-of entity resolution with domain adaptation</article-title>
          ,
          <source>Proc. VLDB Endow</source>
          .
          <volume>15</volume>
          (
          <year>2022</year>
          )
          <fpage>3666</fpage>
          -
          <lpage>3669</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>