<!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>Automatic Identity Recognition in the Semantic Web ?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Al o Ferrara</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Davide Lorusso</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefano Montanelli</string-name>
          <email>montanellig@dico.unimi.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Universita degli Studi di Milano, DICo</institution>
          ,
          <addr-line>10235 Milano</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The OKKAM initiative1 has recently highlighted the need of moving from the traditional web towards a \web of entities", where real-world objects descriptions could be retrieved, univocally identi ed, and shared over the web. In this paper, we propose our vision of the entity recognition problem and, in particular, we propose methods and techniques to capture the \identity" of a real entity in the Semantic Web. We claim that automatic techniques are needed to compare di erent RDF descriptions of a domain with the goal of automatically detect heterogeneous descriptions of the same real-world objects. Problems and techniques to solve them are discussed together with some experimental results on a real case study on web data.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        The Semantic Web is a web of data2, but, we could add, it is (or should be)
also a web on entities. In the Semantic Web context, people and organizations
provide a explicit and semantically rich descriptions of their contents on the web,
enabling human and machine interaction as well as data integration. In doing
this, concrete and abstract real-world entities (e.g., persons, products, locations)
are searchable on the web by exploiting their RDF descriptions. But, obviously,
people perceive and describe the same real entity in many di erent ways. The
risk of this is to produce the so-called \archipelago of semantic islands" [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ],
where each description of the same entity is di erent form the others and where
data and information cannot be integrated and re-used. In other terms, what we
loose here is not the real entity, which is available in many documents in many
ways, but rather the \identity" of the real-entity. Now, what does it mean really
the word \identity"? Despite the philosophical issues behind the question, we
could agree on the fact that the identity is the way we use in order i) to refer
to an object, ii) to distinguish an object from another one, and iii) to collect
and integrate information about an object. This problem has been solved in the
traditional web for what concerns resources and documents by using the URI
standard. The question here is if we can provide something similar to URIs for
entities. If we want to capture the \identity" of a real entity in the Semantic
Web, we need to be able to compare di erent RDF descriptions of a domain with
the goal of automatically detect descriptions referred to the same real-world
object. We call this problem \Identity Recognition Problem". In this paper,
we discuss the identity recognition problem by focusing on three sub-problems
and by proposing speci c methods and techniques to solve them. Moreover,
we present a case study where these techniques are shown in action and some
experimental results are provided by using the instance matching functionalities
implemented in our ontology matching tool HMatch, which is developed in the
framework of the BOEMIE project [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ].
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>The Identity Recognition Problem</title>
      <p>We call individual any abstract or concrete entity in a domain of interest. When
a domain is described by a formal representation of its contents, we do not
have a direct knowledge of the individuals per se, but only a set of descriptions
or perceptions of these individuals. A domain representation is seen as a set of
descriptions. A description is an arbitrary set of assertions about domain objects
and data values speci ed according to a formal language and a data model. In
this respect, the problem of individual identi cation is de ned as:
1. the problem of detecting, out of the several assertions that characterize a
description, those assertions which denote a speci c individual in the domain;
2. the problem of detecting, out of several descriptions in a domain
representation, those descriptions which denote the same individual in the domain.
A domain representation is provided according to a formal language and a data
model. Data provided in the model can be typed and featured by a well de ned
semantics (e.g., DL ontologies), structured by a relational or object-oriented
model (e.g., relational or object-relational databases), or organized as potentially
untyped graphs (e.g., RDF, RDFS). We assume to generalize domain
representations as RDF untyped graphs, where nodes denote objects or atomic data and
edges denote labeled binary relations. To give an example of individual
representations, let us suppose to represent a DVD collection. Two examples of RDF
individual descriptions are the following ones:</p>
      <p>Description 1
h#d01i h#titlei scarface
h#d01i h#directori Brian De Palma
h#d01i h#actori Al Pacino
h#d01i h#actori Michelle Pfei er
h#d01i h#pricei 14.99</p>
      <p>Description 2
h#d01i h#titlei scarface
h#d01i h#directori h#d02i
h#d02i h#namei Brian De Palma
h#d01i h#actori h#d03i
h#d03i h#namei Al Pacino
h#d01i h#actori h#d04i
h#d03i h#namei Michelle Pfei er
h#d01i h#pricei 14.99
Intuitively, we have in both cases a description of a DVD (i.e., d01) and some
data about it. But, how many di erent individuals are represented in the two
descriptions? Which properties are referred to which individual? How can we
detect individuals here?
We can maybe agree on the fact that, in both cases, ve real individuals are
represented: four concrete individuals (i.e., the DVD, the persons Brian De Palma,
Al Pacino and Michelle Pfei er) and an abstract individual (i.e., the movie
\Scarface"). But we have di erent properties in the two cases: title is an attribute of
the DVD or an attribute of the movie \Scarface", or both? Moreover, persons
have a name in the second representation, but no attributes in the rst. Finally,
supposing to have a correct identi cation of individuals in the two cases, how
are we supposed to match these two di erent representations?
We can try to address these questions by splitting the Identity Recognition
Problem into three sub-problems:
1. Individuals identity and essence: what is an individual and how it is
identied?
2. Individuals description: how to compare two di erent descriptions of the
same individual?
3. Individuals existence: how to deal with the fact that some individuals
descriptions \contain" descriptions of other individuals? When an individual
has an independent existence?
In the following sections we try to formalize these problems and sketch possible
techniques to address them.
2.1</p>
      <p>A Real Case Study
In order to test and discuss the techniques proposed in this paper over real data,
we created a case study using data about DVDs provided by the Amazon.com
web service3 together with data provided about movies by the IMDB database4.
The goal of our test case is to identify movies out of these datasources. For what
concerns Amazon, movie identi cation is not trivial, because data describe DVD
editions of the movies and not the movies per se. Thus, we want to cluster
together DVDs referring to the same movie and to extract out of DVD descriptions
the movie description (i.e., extraction). In our ideal case, a user who is going to
create a RDF movie collection would be able to get a reference to \Scarface" by
automatically exploring the Amazon DVD collection. On the other side, IMDB
provides data about movies. In such a case, the goal is to compare IMDB movie
descriptions with movie descriptions extracted from Amazon, in order to
automatically identify di erent descriptions referred to the same real movie (i.e.,
mapping). These two goals are graphically presented in Figure 1.</p>
      <sec id="sec-2-1">
        <title>3 http://aws.amazon.com/</title>
        <p>4 http://imdb.com/. Despite the fact that IMDB is an Amazon.com company, data
provided by the two services are very di erent, at least with respect to the user
query.
Scarface (Widescreen Anniversary Edition)</p>
        <p>DVD 2003
Scarface (Platinum Edition)</p>
        <p>DVD 2006</p>
        <p>Extraction
Scarface
(1983)</p>
        <p>Identification</p>
        <p>Scarface
(1932)
?
Scarface (1983)</p>
        <p>Scarface (1932)
aka: Scarface, the Shame of the Nation</p>
        <p>Scarface (1982) - TV</p>
        <p>Scarface
DVD 2003</p>
        <p>"Scarface"
Scarface (1928)</p>
        <p>us.imdb.com</p>
        <p>In order to evaluate our techniques, we manually built a set of expected
results. From Amazon, we got data resulting for the query \Scarface" over the
DVDs collection. Results contain 87 items (describing videos and DVDs).
Manually, we categorized these items with respect to the related movie: we obtained 15
DVD editions of the movie \Scarface (1983)", 4 of the movie \Scarface (1932)",
6 DVD collections including the movie \Scarface (1983)", 11 of the movie \Mr.
Scarface (1976)", 4 of the movie \Captain Scarface (1953)" and 47 DVD editions
of other movies/materials not directly related to the query \Scarface".
Concerning IMDB, we collected 27 movies, including the ones in Amazon and others.
Finally, we imported data into two very simple RDF schemas, with the goal of
preserving as much as possible the original structure of data provided by the
two resources. A portion of resulting RDF is shown in Figure 2.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Identity of Individuals</title>
      <p>
        In general, when looking at a real individual we focus on some of its properties
in order to distinguish it from other individuals. However, not all the individual
properties can be used to perform such a distinction. In the Aristotelian theory of
de nition, some properties are considered as part of the individual essence, some
h#item-2i h#titlei Scarface, Special Edition
h#item-2i h#directori Brian De Palma
h#item-2i h#actori Al Pacino
h#item-2i h#formati PAL
h#item-2i h#hasLanguagei h#L06i
h#L06i h#namei Spanish
h#M-01i h#titlei Scarface (1983)
h#M-01i h#directori h#P04i
h#M-01i h#casti h#C06i
h#P04i h#namei Brian De Palma
h#P04i h#birthi 11-09-1940
h#C06i h#actori h#P16i
h#C06i h#characteri Tony Montana
h#P16i h#namei Al Pacino
other are just \accidental" attributes. Borrowing this intuition, we can assume
that, given an individual description Do = fA0; A1; : : : ; Ang as a set of assertions
about an individual o, the identi cation Io of o is an identity function Io(Do) !
f(di; vi)g which associates to each group of assertions in Do an identi cation
strength vi in the range [
        <xref ref-type="bibr" rid="ref1">0,1</xref>
        ]. Goal of the identi cation function is to provide a
measure of the importance of each group of assertions with respect to the general
goal of detecting the identity of o.
      </p>
      <p>
        De nition 1. Identity Function. Given an individual description D = fA0; A1;
: : : ; Ang, the Identity Function I(D) ! f(di; vi)g is de ned as follows:
8di 2 P(D); di ! vi
where P(D) denotes the power set of D, di denotes a possible subset of assertions
in D, while vi is a measure (in the range [
        <xref ref-type="bibr" rid="ref1">0,1</xref>
        ]) of the importance of di for the
identi cation of o.
3.1
      </p>
      <p>Implementation of the Identity Function
The identity function can be obtained in three di erent ways:
1. by taking into account schema constraints when available (e.g., functional
properties in DL, key constraints in relational databases);
2. by taking into account domain speci c information or human suggestions
(e.g., ISBN codes for books, personal identi cation numbers for persons,
manual con guration of an identity recognition system);
3. by exploiting statistical techniques over data values. Usually, the idea behind
these techniques is that assertions with a high number of di erent values are
more useful for identi cation than assertions with a high number of similar
or equal values.</p>
      <p>In HMatch, identifying properties can be manually chosen or automatically
detected by taking into account, for each group of assertions d 2 D, the number
tNh6=de goifvedni oenreen.tMvoarleuefosrrmetarlileyv,egdivfeonr adniinndailvlitdhuealinod, iwviedtuaaklse oinfttohaecscaomunet ttyhpeeseotf
O of all the individuals of the same type of o in the RDF description. Then, we
calculate the identity function as follows:
8di 2 P(D); di !</p>
      <p>N=di</p>
      <p>6
j OP j
where N6=di is the number of di erent values of the assertions di over the set O,
while j OP j is the number of di erent properties featuring the individuals in O.
Example. To see how the function works, let us suppose to have three simple
movie descriptions:
h#M01i h#titlei Scarface h#M02i h#titlei Scarface h#M03i h#titlei Testament
h#M01i h#yeari 1983 h#M02i h#yeari 1932 h#M03i h#yeari 1983
h#M01i h#genrei Crime</p>
      <p>By taking into account all possible subsets of movie properties, the results
of the identi cation function is shown in Table 1.</p>
      <p>Looking at the results, we can see how the function does not take into account
properties with missing values, because they do not provide useful information.
Moreover, the title or the year are not useful if we consider them separated, but
they are enough to identify movies when taken into account in combination.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Heterogeneous Individual Descriptions</title>
      <p>The same individual can be described in many di erent ways. Descriptions of
the same individual can be di erent for several reasons, including the use of
di erent languages or data models and a di erent conceptualization of the same
domain. The use of a generalized RDF model does not avoid the presence of
heterogeneous descriptions of the same individual. Thus, a key requirement in
individual identi cation is the capability of comparing heterogeneous
descriptions of the individuals in order to cluster together similar or matching
descriptions. Given an individual o and two descriptions Do1 = fA0; A11; : : : ; Ang and
1 1
Do2 = fA0; A12; : : : ; A2mg of o, the identi cation Io of o is a matching function
2
Io(Do1; Do2) ! (D1;2; v). Goal of the function Io(Do1; Do2) is to understand when
two descriptions denote the same real individual in the domain.
De nition 2. Matching Function. Given two individual descriptions D1 and
D2, the matching function I(D1; D2) is de ned as follows:</p>
      <p>
        I(D1; D2) ! (D1;2; v);
where v is a measure in the range [
        <xref ref-type="bibr" rid="ref1">0,1</xref>
        ] of the similarity of D1 and D2 and D1;2
is the set of assertion mappings between D1 and D2. The goal of the
matching function is to provide a measure of similarity between D1 and D2, under
the assumption that the higher the descriptions similarity is, the higher is the
probability that D1 and D2 denote the same real individual.
4.1
      </p>
      <p>
        Implementation of the Matching Function
A typical implementation of the matching function is based on the idea of
comparing the data values associated with a given individual. But, since di erent
descriptions may have a di erent structure, how can we know which graph nodes
in the two descriptions should be compared? The approach used in HMatch is to
rely on the results provided by matching the two datasource schemas. In order to
deal with highly di erent data structures, we need complex mappings between
the concepts and properties of the two schemas. HMatch itself implements
several di erent techniques for schema matching, including linguistic, structural and
contextual matching [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Many other techniques have been proposed for schema
matching [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Since schema matching is not the goal of the paper, we present
the instance matching approach used in HMatch by assuming to have complex
mappings at the schema level. HMatch evaluates the degree of similarity among
di erent individuals by considering those assertions which provide a description
of the individuals features. Consequently, the similarity of role ller values as
well as the similarity of their direct types is evaluated. When two instances are
compared, their similarity is proportional to the number of similar roles and role
llers they share. Moreover, for the similarity evaluation we use the identi cation
power of properties provided by the identity function. The approach adopted in
HMatch is based on the idea of considering properties as connections between
individuals and propagating similarity values through them. Each speci cation
of an individual is represented by means of a tree. In order to evaluate the degree
of similarity of two individuals, the procedure computes a measure of similarity
between datatype values and propagates these similarity degrees to the
individuals of the higher level by combining the similarity among their property llers.
To this end, HMatch provides a set of speci c techniques devoted to the
evaluation of similarity between datatype values. A function called datatype role ller
matching is responsible of selecting the most suitable matching technique for
each pair of datatype role llers, according to the semantic meaning of the roles
and to the datatype category.
      </p>
      <p>Example . Consider two individuals item-1 and M-01 representing di erent RDF
descriptions of the movie Scarface (Figure 3). item-1 describes a DVD sold by
Amazon while M-01 describes directly the movie.</p>
      <p>Amazon item</p>
      <p>
        First of all we suppose to have the following set of mappings at schema level
produced by a schema matching tool: f(title,title), (director, director ), (actor,
actor.name), (theatricalReleaseDate, Year )g. These mappings reduce the nested
structure of the M-01 description to a at one, making the M-01 description
more comparable with the one of item-1. For each pair of properties involved
in a mapping, HMatch compares the two values by means of a matching
function speci c for the category of the property (e.g. person name, date), which
produces a similarity measure in the range [
        <xref ref-type="bibr" rid="ref1">0,1</xref>
        ]. The two property values are
considered similar if the similarity measure is greater then a given threshold.
For instance, the comparison of (Amazon) director and (IMBD) director
property values, which are \Brian De Palma" and \De Palma, Brian" respectively, is
performed with a matching function for person names and produces a similarity
measure of 0.9. When multiple values are de ned for the same properties, as for
actor and actor.name, each possible value of the rst property is compared with
each possible value of the second. Then a set similarity measure is produced by
considering similar values as the intersection of the two sets. When all the values
of mapped property have been compared, the overall similarity measure of the
two individuals is computed with the dice coe cient method. Assuming that,
after all the comparisons, M-01 and item-1 have similar values for the properties
(director, director), (actor, actor.name) and (theatricalReleaseDate, Year), but
not for the properties (title,title), the overall similarity of the two individuals is
evaluated as follows:
      </p>
      <p>Having a reasonable threshold value of 0.6, the two individual descriptions
are considered similar, which is correct since they are referred to the same movie.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Autonomous Identity</title>
      <p>
        In the two previous sections, we assumed to work with individual descriptions.
But, a description is just an arbitrary collection of assertions. So, the problem
here is: how can we select the minimal set of assertions describing an individual?
In other terms, we could also wondering if there is a method to identify an
autonomous individual out of a domain representation. The most simple intuition
here is to consider all the assertions having the same domain object as subject.
This method can be easily generalized to cope with more nested graph structures,
by taking into account all the assertions that are directly or indirectly connected
with a domain object. However, this approach is not su cient in many cases.
This problem can be introduced by looking at the example of Figure 4. The two
descriptions in the example represent two di erent DVD editions of the same
movie. This means that there is a real individual (i.e., the movie \Scarface")
which is not represented by a speci c description. In general, a good design of
the source schema should avoid this anomalies, but in real data it happens very
often to have individuals that are \hidden" into descriptions of other individuals.
For example, when talking about books, movies, music works and other kind of
abstract individuals, it happens that the work is not distinguished from its
physical edition. Also in other domains this is a problem: we have persons descriptions
hidden into business transaction descriptions, geographical locations hidden into
travel descriptions, and so on. How can we deal with this kind of individuals?
In this context, the identity Io of an hidden individual o is a discovery function
Io(D) ! f(di; vi)g which is de ned as follows:
De nition 3. Discovery Function. Given an arbitrary description D, the
discovery function Io(D) ! (di; vi) is de ned as:
where di denotes a possible subset of assertions of D and vi (in the range [
        <xref ref-type="bibr" rid="ref1">0,1</xref>
        ])
denotes the probability of di to be the description of an hidden individual o.
In HMatch, the discovery function is implemented using matching. The idea is to
execute matching over the same datasource by collecting a log of the properties
matching. Intuitively, in such a way we collect the properties that, in most of the
cases, have equal or similar values in a set O of individuals. Of course, there are
several properties whose values match in many cases even if they do not denote
an autonomous individual. For example, the format of a DVD (e.g., PAL) is
the same in many cases, even if it does not denote a movie. To deal with this
situation, we work under the assumption that only a signi cant group of
properties matching together in many cases are denoting an autonomous individual.
We nd all the subsets of properties matching and, for each subset di, we take
into account the number of properties in the subset (j di j) and the number of
occurrences of matching values vi of the properties in the subset over O. Given
the subset dmax as the subset containing the maximum number of properties,
we associate with di the measure di = jdj . Analogously, given the maximum
jdmaxj
number of matching values occurrences vmax, we associate with di the measure
vi . As a result, given the subset of matching properties di, its measure
vi = vmax
of discovery D(di) is calculated as:
      </p>
      <p>D(di) = di + vi:
In such a way, we consider the subset with the best balance between the number
of properties and the number of matching values over its properties as the set
of properties candidate to denote an autonomous individual description within
a description of other individuals.</p>
      <p>Example. As an example, we take into account the example of Figure 4. Matching
description 1 against description 2, we obtain the following mappings:
f(A1; A2); (E1; E2); (F 1; F 2); (G1; G2)g
leading to the following subset of matching properties:</p>
      <p>d = f#title; #director; #actorg:
Since the example is very simple, it is easy to see how d is also the best candidate
to denote an autonomous individual. In more complex situations, this approach
can fail due to some properties in the candidate set which are in fact useless to
individual discovery. However, the resulting candidate set can be used to perform
matching again by considering only the properties in the candidate set, in order
to verify the quality of the obtained results. A more detailed discussion on this
is provided in the following section.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Experimental Results</title>
      <p>In order to evaluate the proposed techniques, we take into account the case
study presented in Section 2.1. In particular, we have two goals: i) we want to
discover movies within Amazon.com DVD data; ii) we want to compare movie
descriptions discovered in Amazon.com against movies in IMDB, in order to nd
di erent descriptions of the same real movies.
6.1</p>
      <p>Discovery Test Case
Concerning the rst goal, our approach for testing is to match all the DVD
descriptions extracted from Amazon.com in order to nd correspondences (i.e.,
mappings) among DVDs containing the same movie. The ground truth has been
created by manually clustering DVDs with respect to the movie and by creating
the set of expected mappings. It is important to stress that the goal here is not
to nd similar or equal DVDs, but DVDs, potentially di erent, with the same
movie. This means that some data referred to the product, such as ISBN, is
not useful to our needs. Moreover, data are quite \dirty" because they contain
errors or incomplete information. Thus, we performed two preliminary
operations: rst, we execute matching by considering all the properties, in order to
have a measure of how the discovery works without a set of properties that
denote the autonomous individual movie (Test 1); second, we manually select the
set of DVD properties referred to movies, and we execute matching again. This
provides a measure of how the matching works in the ideal situation, when the
relevant properties denoting movies in DVD descriptions are correctly selected
(Test 3). Finally, we exploited the discovery function of HMatch to
automatically retrieve the relevant properties for movies and we execute the matching
by considering only the relevant properties (Test 2). In order to evaluate the
quality of the results we used three measures: precision, de ned as the quantity
of retrieved mappings that are correct, and recall, de ned as the quantity of
correct mappings that are retrieved, and F-Measure which is the harmonic mean
of the two. Results are shown in Table 2, where, for each Test, we provide two
measures in the form X (Y), where X is the absolute value of precision or recall,
while Y is the value of precision and recall with respect to the ideal matching
case (Test 3).</p>
      <p>
        The results show how matching over all the DVD properties is useless with
respect to the goal of discovering movies. In fact, many DVD are similar
because of properties like the format which is not relevant neither for the DVD
identi cation nor for the movie identi cation. So, this method (Test 1) produces
a high number of mappings, leading to a high recall with a very low precision.
On the other way, manual selection of properties (Test 3) produces the best
results that can be obtained by using matching for movie discovery. These
results are characterized by a good precision and an average recall. This means
that when we collect together DVDs with the same movie, it is quite probable
that the collection is correct, even if some DVD is missing. The results obtained
with the discovery function (Test 2) are promising because, despite the fact that
the method is completely automatic, we obtained quite good precision and recall
results, especially if compared with the ones obtained with the manual approach.
The matching test case has been executed by taking onto account data
extracted from Amazon together with data provided by IMDB. The goal here is
to evaluate in terms of precision and recall the quality of the results obtained
using HMatch for individual comparison. In particular, we want to check if our
instance matching techniques are suitable for automatically retrieve di erent
descriptions denoting the same real entity (i.e., a movie). The ground truth has
been de ned by manually comparing the 27 movies retrieved in IMDB against
the 87 DVDs retrieved on Amazon for the query \Scarface". In particular, we
have manually mapped each movie with all the DVDs containing that movie.
Then, we have executed HMatch by taking into account only the properties
selected in the previous discovery test (Test 2). The results in terms of precision,
recall and F-Measure are shown in Table 3.
In the paper, we have seen how instance matching techniques are crucial for
solving the identity recognition problem by exploiting automatic techniques.
In general, instance matching is frequently referred to as an Entity Resolution
problem (also called Deduplication or reference reconciliation) and it is de ned
as the process of identifying and merging records judged to represent the same
real-world entity. Up to now, the instance matching problem has been recognized
as particularly relevant in database and data integration applications where it
is referred to as record linkage and it is de ned as the task of quickly and
accurately identifying records corresponding to the same entity from one or more
data sources [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        A rst important category of approaches to record linkage rely on statistical
theories and techniques. In particular the problem is translated in a Bayesian
inference problem [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] by means of decision rules based on probabilities, which
are estimated using di erent techniques such as expectation maximization
algorithms [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], with some further improvements in order to manage missing values
and costs of misclassi cation. More recent approaches to record linkage are based
on classi cation techniques in the machine learning. The supervised learning
systems rely on the existence of training data in the form of record pairs, prelabeled
as matching or not. When this kind of information is not available, other
techniques must be adopted to detect matching records. In general these techniques
de ne a distance metric for records which does not need tuning through
training data. A simple approach is to consider a record as a unique string and to
apply known edit-distance metrics [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] but, in such a way, references between
di erent records are ignored. Ananthakrishna et al. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] describe a similarity
metric that uses not only the textual similarity, but the co-occurrence similarity of
two entries in a database. A similar way to improve the comparison metrics is
the one by Felix Naumann et al. on data fusion [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. The similarity evaluation
of two record is enhanced by the analysis of the context of a record, which is
captured by considering not only the signi cant attributes of a record but also
those attributes related to it through a foreign key. Naumann et al. exploit
duplicate detection also to support schema matching functionalities. Halevy et al.
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] proposed an algorithm that, besides the exploitation of co-references among
records, propagates information between reconciliation decisions of di erent
descriptions to accumulate positive and negative evidences. Then, the algorithm
gradually enriches references by merging attribute values. Our approach for
instance matching has a similar strategy but we do not limit the context analysis
to a single level of similarity propagation because the ontology instances
generally have a more nested, tree-like, structure and the meaningful data is at
the bottom of it. For this reason, ontology instance matching require more
sophisticated techniques for handling the propagation of the similarity measure at
the instance level. Moreover, for expressive languages (i.e. DLs) the structure of
instances is not explicit and should be derived by reasoning.
      </p>
      <p>
        In the Semantic Web the attention on instances for the purpose of ontology
matching has been poorly studied and only basic techniques for ontology instance
matching have been proposed. For example, in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] instances are considered to
support/validate concept matching techniques trough statistical analysis. This
means that the similarity between two concepts is evaluated by measuring the
\signi cance" in the overlap of their respective instance sets [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. To this end,
various similarity metrics have been proposed to evaluate instance similarity
and thus instance-based concept matching [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Another important application
of instance matching is ontology evolution, which means the need of supporting
experts in managing ontology changes through advanced and possibly automated
techniques. This is the case of the BOEMIE project (Bootstrapping Ontology
Evolution with Multimedia Information Extraction) where a novel methodology
for ontology evolution is de ned to enhance traditional approaches and to provide
methods and techniques for evolving a domain ontology through acquisition
of semantic information from multimedia resources such as image, video, and
audio [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
8
      </p>
    </sec>
    <sec id="sec-7">
      <title>Concluding Remarks</title>
      <p>In this paper, we have discussed the problem of identity and entity recognition
in the semantic web, by presenting three main sub-problems and by
providing speci c techniques to solve them. Our thesis is that instance matching and
related techniques can be used to support entity recognition by enabling the
automatic discovery of \hidden" entities as well as the automatic comparison of
di erent descriptions of the same real-world objects. To this end we have
presented promising experimental results. Concerning scalability, which is a crucial
issue for semantic web applications, we are currently performing tests with larger
datasets and our future work will be focused on optimization of the algorithms
in terms of computational performances. Moreover we are collecting more
experimental data in the BOEMIE European Project 5, where instance matching is
used with the purpose of retrieving descriptions of the same entities over
semantic data extracted from multimedia resources. BOEMIE provides methods and
techniques for knowledge acquisition from multimedia content, by introducing
the notion of evolving multimedia ontologies, which is used for the extraction of
information from multimedia content in networked sources. In particular,
multimedia resources are analyzed with the goal of providing a semantic description
of their content. The result of this process is the population of an OWL ontology.
In the process of population, di erent instances created from di erent resources
are grouped together if they denote the same real-world object. Our current and
future work in the project is to investigate, develop and test advanced instance
matching techniques as a support for ontology population.</p>
      <sec id="sec-7-1">
        <title>5 http://www.boemie.org</title>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bouquet</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stoermer</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mancioppi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giacomuzzi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          : OkkaM:
          <article-title>Towards a Solution to the \Identity Crisis" on the Semantic Web</article-title>
          .
          <source>In: Proc. of the 3rd Italian Semantic Web Workshop (SWAP</source>
          <year>2006</year>
          ), Pisa, Italy,
          <string-name>
            <surname>CEUR</surname>
          </string-name>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Castano</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferrara</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Montanelli</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Matching ontologies in open networked systems: Techniques and applications</article-title>
          .
          <source>Journal on Data Semantics (JoDS)</source>
          V (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bruno</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Castano</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferrara</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lorusso</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Messa</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Montanelli</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          : Ontology Coordination Tools:
          <article-title>Version 2</article-title>
          .
          <source>Technical Report D4</source>
          .7,
          <string-name>
            <given-names>BOEMIE</given-names>
            <surname>Project</surname>
          </string-name>
          ,
          <fpage>FP6</fpage>
          -
          <volume>027538</volume>
          , 6th EU Framework Programme (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Euzenat</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shvaiko</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : Ontology Matching. Springer-Verlag (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Elmagarmid</surname>
            ,
            <given-names>A.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ipeirotis</surname>
            ,
            <given-names>P.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Verykios</surname>
            ,
            <given-names>V.S.:</given-names>
          </string-name>
          <article-title>Duplicate record detection: A survey</article-title>
          .
          <source>IEEE Transactions on Knowledge and Data Engineering</source>
          <volume>19</volume>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Fellegi</surname>
            ,
            <given-names>I.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sunter</surname>
            ,
            <given-names>A.B.</given-names>
          </string-name>
          :
          <article-title>A theory for record linkage</article-title>
          .
          <source>Journal of the American Statistical Association</source>
          <volume>64</volume>
          (
          <year>1969</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Winkler</surname>
          </string-name>
          , W.:
          <article-title>Improved decision rules in the fellegi-sunter model of record linkage</article-title>
          .
          <source>In: Proceedings of the Section on Survey Research Methods</source>
          . (
          <year>1993</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Monge</surname>
            ,
            <given-names>A.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Elkan</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>An e cient domain-independent algorithm for detecting approximately duplicate database records</article-title>
          .
          <source>In: Research Issues on Data Mining and Knowledge Discovery</source>
          . (
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Ananthakrishna</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chaudhuri</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ganti</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Eliminating fuzzy duplicates in data warehouses</article-title>
          .
          <source>In: In Proceedings of the 28th International Conference on Very Large Databases (VLDB</source>
          <year>2002</year>
          ).
          <article-title>(</article-title>
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Naumann</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bilke</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bleiholder</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weis</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Data fusion in three steps: Resolving schema, tuple, and value inconsistencies</article-title>
          .
          <source>IEEE Data Eng. Bull</source>
          .
          <volume>29</volume>
          (
          <year>2006</year>
          )
          <volume>21</volume>
          {
          <fpage>31</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Dong</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Halevy</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Madhavan</surname>
          </string-name>
          , J.:
          <article-title>Reference Reconciliation in Complex Information Spaces</article-title>
          .
          <source>In: Proc. of the ACM SIGMOD Int. Conference on Management of Data</source>
          , Baltimore, Maryland, USA (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lu</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , Zhang, G.:
          <article-title>Integration of Ontology Data through Learning Instance Matching</article-title>
          .
          <source>In: Proc. of the IEEE Int. Conference on Web Intelligence (WI'06)</source>
          , Hong Kong,
          <string-name>
            <surname>China</surname>
          </string-name>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Isaac</surname>
          </string-name>
          , A.,
          <string-name>
            <surname>van der Meij</surname>
          </string-name>
          , L.,
          <string-name>
            <surname>Schlobach</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>An Empirical Study of Instance-Based Ontology Matching</article-title>
          .
          <source>In: Proc. of the 6th Int. Semantic Web Conference, 2nd Asian Semantic Web Conference (ISWC</source>
          <year>2007</year>
          +
          <article-title>ASWC 2007)</article-title>
          , Busan, Korea (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Engmann</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Massmann</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>Instance Matching with COMA++</article-title>
          .
          <source>In: Proc. of the Workshop on Datenbanksysteme in Business, Technologie und Web (BTW</source>
          <year>2007</year>
          ), Aachen, Germany (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Castano</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Espinosa</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferrara</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karkaletsis</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kaya</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Melzer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , Moller, R.,
          <string-name>
            <surname>Montanelli</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petasis</surname>
          </string-name>
          , G.:
          <article-title>Multimedia Interpretation for Dynamic Ontology Evolution</article-title>
          .
          <article-title>Journal of Logic and Computation, special issue on Ontology Dynamics (</article-title>
          <year>2008</year>
          ) To appear.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>