<!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>Modeling and Publishing Finnish Person Names as a Linked Open Data Ontology</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Helsinki Centre for Digital Humanities, University of Helsinki</institution>
          ,
          <country country="FI">Finland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Semantic Computing Research Group (SeCo), Aalto University</institution>
          ,
          <country country="FI">Finland</country>
        </aff>
      </contrib-group>
      <fpage>3</fpage>
      <lpage>14</lpage>
      <abstract>
        <p>This paper presents an ontology and a Linked Open Data service of tens of thousands of Finnish person names, extracted from contemporary and historical name registries. The repository, rst of its kind available, is intended for Named Entity Recognition and Linking in automatic annotation and data anonymization tasks, as well as for enriching data in, e.g., genealogical research.3 Actor ontologies of people, groups, and organizations (e.g., Getty ULAN4), also called authority les [11] in Library Sciences, are a key ingredient needed in publishing and using Cultural Heritage (CH) Linked Data on the Semantic Web. For representing actor ontologies, there exists several vocabularies, such as FOAF5, REL6, BIO7, and Schema.org [6]. Actor ontologies make a distinction between language-neutral concepts (resources identi ed by IRIs) and their literal names. In Resource Description Framework (RDF)8-based modeling in use on the Semantic Web, only resources can have properties while literal names are considered only atomic data that do not have properties, except a possible datatype and language tag attached. However, in many cases also literal words can have quali ers and properties: names of things change in time and in context, e.g., female names due to marriage, or the language version form of the name in di erent countries and cultures (e.g., \Gabriela" vs. \Gabriele"). In linguistic Linked Data repositories [22], modeling phenomena related to the properties of words instead of real world things is actually the main reason for the research. For modeling phenomena like this, the SKOS recommendation has been extended to</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>SKOS-XL9, allowing specifying properties for literal SKOS labels, and various
linguistic ontology models such as Lemon10 and OntoLex-Lemon11 have been
devised for representing linguistic Linked Data repositories.</p>
      <p>A person name individualizes and identi es an individual. A person name
ontology is a collection of contemporary and historical person names in a
machineunderstandable way. It is a knowledge graph describing names, their features,
and usage in di erent datasets. In actor ontologies of people, names are often
represented as literals. The features of the name are often ignored when
describing people in actor ontologies although the name can carry information about
its bearer such as socioeconomic status or gender.</p>
      <p>
        This paper introduces a data model for representing person names as an
ontology, based on tens of thousands of person names from contemporary Finnish
name registries, including also historical names extracted from various CH linked
data sources. The new Finnish Linked Open Data name ontology HENKO12 has
been used as a basis for named entity recognition (NER) and linking tasks [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]
in automatic content annotation [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ] and data anonymization services [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ], as
well as enriching linked data for applications, such as genealogical network
analysis [
        <xref ref-type="bibr" rid="ref16 ref20">16,20</xref>
        ]. To foster the reuse of the data, this repository of Finnish person
name data, rst of its kind available, is published as a Linked Open Data service
for application developers to use under the open CC BY 4.0 license.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Datasets</title>
      <p>The data for the person name ontology HENKO was collected from multiple
registries. It consists of given and family names and the number of users per
name. The amount of users for the given names was calculated by gender. In
addition, the given names data included the sum of users who have it as a rst
and as other given name. The collected datasets, the total number of names, and
number of unique names in the data are shown in Table 1.</p>
      <p>The rst dataset in the table is from the Finnish Digital Agency13 (FDA),
a governmental agency that promotes digitalization of society, secures the
availability of data, and provides services for the life events of its customers. The
agency publishes Finnish name data as open data in the governmental
publication portal avoindata. 14. This dataset contains given names that are used
by a minimum of ve persons, and family names for the minimum of 20
persons. There are in total 23 018 family names, 9507 male given names, and 12 304
female given names (cf. Table 1). According to the product manager of FDA,
the dataset contains only a fraction of Finnish person names. The full registry
9 https://www.w3.org/TR/skos-reference/skos-xl.html
10 https://lemon-model.net
11 https://www.w3.org/2019/09/lexicog/
12 The name comes from the Finnish name Henkilonimiontologia (Person name
ontology); Henko is also a diminutive form of the name Henrik.
13 https://dvv.fi/en/individuals
14 https://www.avoindata.fi/data/en_GB/dataset/none
contains a total of 293 367 family names and 126 119 given names. According to
FDA, the names used by less than the given amounts, are not publicly available
because rare names can single out individual persons violating their privacy.
Most of these unique names come from foreigners, and the rarer Finnish given
names are often compound or coined names. FDA publishes the data twice a
year; our the data has been collected starting from August 2018.</p>
      <p>Dataset uFnaimquiley ntaotmales
The Finnish Digital Agency 16 931 23 018
BiographySampo 1205 5535
Norssi High School Alumni 1002 4598
AcademySampo 6721 11 016
unGiqiuveefnemnaalmemesale Total
18 206 11 093 8299 42 410
805 1705 1761 9001
233 509 1039 6146
946 1389 1423 13 828</p>
      <p>
        In addition to using the FDA data, our ontology has names extracted from
the datasets Norssi High School Alumni on the Semantic Web [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ],
BiographySampo [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], and AcademySampo [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]15. AcademySampo contains names of
university students from 1640 to 1899, and it contains plenty of historical,
often Latin-based, names. BiographySampo data is based on 13 100 biographies of
signi cant Finns throughout the history from the 3rd century to present time,
and it has many Swedish names used by nobility and upper class because until
1809 Finland was an integral part of Sweden. The Norssi Alumni dataset records
students in a Finnish school from 1867 to 1992 and the unique names in it are
mostly rare Finnish names. Altogether these datasets provided 15 975 distinct
family names, 2791 male and 2500 female names.
      </p>
      <p>
        In order to have more features for the names in the ontology, the name
datasets were processed and enriched using natural language processing (NLP)
methods. Family names, for example, can contain nobiliary particles or su xes.
In Finnish family names [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ] nobiliary particles are not used, but the names
have su xes that have indicated once if a person came from a place (e.g.,
sufxes -la, -la), or person's socioeconomic status (e.g., scholars, soldiers, clergy
with su xes -er , -ius). To make this information explicit, the particles and
sufxes were extracted from the names. For the particle extraction, the corpus
of particles (in other languages) was compiled from the website of the
Institute for the Languages of Finland (Kotus)16 to identify names that contain
particles. The extraction of su xes was done using Lexical Analysis Service's
(LAS)17 [
        <xref ref-type="bibr" rid="ref18 ref19">18,19</xref>
        ] language recognition service, hyphenation service, and a
manually compiled stopword list of words in Finnish and Swedish compound names
15 https://seco.cs.aalto.fi/projects/yo-matrikkelit/en/
16 http://www.kielitoimistonohjepankki.fi/ohje/65
17 http://demo.seco.tkk.fi/las/
(e.g., . Mansikkamaa eng. strawberry eld ). The process rst lters out names
ending with a stopword, then detects the language, and lastly hyphenates the
name. The last syllable is recorded as the su x. Short names with only two
syllables were ignored because they rarely end with a su x.
      </p>
      <p>In addition the NLP methods were used in identifying patronymics (e.g.,
Jaakonpoika, eng. son of Jaakko) and matronymics (e.g., Liisantytar, eng.
daughter of Liisa). The matronymics and patronymics are identi ed in Finnish, Swedish,
and Russian. In Finnish and Swedish they end with a word that indicates if its
owner is a female (sv. -dotter, . -tytar ) or a male (sv. -son, . -poika) whereas
the Russian counterparts have a gendered su x (e.g., -ov, -ova). The preceding
part of the word is a person name typically in the genitive case and it can belong
to an ancestor of the person. The ancestor's name wass extracted from the
preceding part and baseformed with the LAS lemmatization tool. Afterwards, the
ancestor's name is used to nd names with the same string form. If the name
exists, the application identi es the gender by using the existing data. The name
instance is typed as matronymic or patronymic depending on the result.</p>
      <p>
        Lastly, the names of HENKO data were linked to their counterparts in
DBpedia and Wikidata to enrich the data with etymological information and
relations to other names. The names were also linked to the bearers of the names
in the source datasets (AcademySampo, BiographySampo, and Norssi Alumni).
In addition, the family names can reference place and vocation names [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ]. To
identify names that refer to places and vocations, the names were linked to the
YSO places ontology18 (Finnish and Swedish place names) and to the Finnish
historical occupations ontology AMMO [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. This information is not only
interesting topical information but can be used in tasks such as linking based NER
to identify names that can be place or vocation names.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>A Data Model for Person Names</title>
      <p>The data model for person names in HENKO has been created based on the
enriched name data. The data model is depicted in Fig. 1. The model has a class
for the written representations of the name, the WrittenNameForm, that includes
the string presentation of the name. Its instances are also instances of the CIDOC
CRM's class E41 Appellation in order to enable the modeling of names and
their alternative forms. This is needed, for example, if a name is translated from
Russian to Finnish, as was the case with the Russian tsars Alexandr I-III, that
were called in Finnish Aleksanteri I-III. The WrittenNameForm class connects
to the GivenName and FamilyName classes via isGivenName and isFamilyName
properties accordingly.</p>
      <p>
        The GivenName and FamilyName classes are subclasses of the Name class.
The Name class describes the basic features of the names, such as properties
for linking both names to their equivalent representations in other ontologies,
to people in other actor ontologies with the same names, in case of compound
18 https://finto.fi/yso-paikat/en/
names by linking it to the parts (e.g., the name Henna-Maria can be linked to
Henna and Maria), and to linguistic information, such as name su xes. Like
in the Wikidata [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] model, the GivenName class has information about the
gender (male, female, unisex) that is inferred for each instance based on the
name usage data. The FamilyName class instances contain information about
the nobiliary particle, such as von, or de la. Initially, the OntoLex-Lemon [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ]
and MMoOn [
        <xref ref-type="bibr" rid="ref13 ref14">14,13</xref>
        ] ontologies were considered for modeling the particles and
a xes, but the models did not t the needs of HENKO because of being too
complex or lacking in features to represent them. In addition, the references
to places and vocations have been recorded using their own properties. Middle
names19 are not common in Finland and are ignored currently in the processing.
      </p>
      <p>The GivenName and FamilyName classes are connected to the
GivenNameUsage and the FamilyNameUsage classes through the isUsed property. These
classes describe the calculated usage of the name. They are the subclasses of
NameUsage class. The NameUsage class describes the general characteristics
of its subclasses, such as count (how often a name is used) and source (data
source for the information). The GivenNameUsage class also separates whether
the name has been used as a rst name or other name (second, third) in
ad19 https://en.wikipedia.org/wiki/Middle_name
dition to having the gender attribute. The DataSource class, that connects to
the NameUsage superclass, describes the used sources in more detail. It includes
attributes such as date (creation time of the data), URL (where the data was
retrieved), temporal information about the dataset, its publisher, and name. The
DataSource class is also connected directly to the WrittenNameForm class.</p>
      <p>Finally, the MatronymicForm and PatronymicForm classes are subclasses of
the class WrittenNameForm. If the instances of the WrittenNameForm class
have been identi ed as patronymics or matronymics, the WrittenNameForm
instances are complemented with information about the origin (Finnish, Swedish,
Russian) and are linked to the given name of the ancestor (GivenName class
instance) using using Wikidata's property \patronym or matronym for this name".
The su xes from the Russian origin names are recorded using the Name class
property su x.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Use Cases</title>
      <p>This section presents the applications of HENKO in automatic annotation tasks.
The applications are available as part of the SeCo Text Annotation Service20.
Gender Identi cation Service The code behind the service21 has been
developed in the projects Norssi Alumni, BiographySampo, and AcademySampo to
determine the gender by person's name. The service uses HENKO vocabularies
of given names containing the frequencies of how often each name appears as a
male or a female name.</p>
      <p>The decision is based on the standard Bayesian approach described in
equations 1 and 2. Equation 1 de nes the probability ( jn) that a person with
a single given name n has gender 2 f"Female", "Male"g. DF (name) and
DM (name) are the frequencies of the name in the vocabularies of female DF
and male DM names. The smoothing variable prevents the probabilities from
getting near-zero values in ambiguous cases. In this way, e.g., names with only a
few samples do not a ect the nal result too much. Likewise, if a name does not
appear in either vocabulary, the estimate reduces to 50%|a natural choice for
a prior probability when estimating an unknown gender. Equation 2 de nes the
probability that a given sequence of names N = (name1; name2; : : :) relates to
gender . To simplify the calculations, the correlation between the names in the
sequence was theorized to be statistically independent, e.g., having name1 would
not correlate with having name2. Besides, the used vocabularies do not include
information about the co-occurrences of given names. Therefore the probability
of a sequence could be calculated as a product of the probabilities for each name.
( jname) =
(namej )
(name)
( )</p>
      <p>D (name) +
DF (name) + DM (name) + 2
(1)
20 https://nlp.ldf.fi
21 http://nlp.ldf.fi/gender-identification
( jN = (name1; name2; : : :)) =</p>
      <p>Q
n2N</p>
      <p>Q ( jn)
n2N
("Female"jn) + Q
n2N
("Male"jn)
(2)</p>
      <p>For the nal decision making, a threshold value (e.g., = 0:75) is used.
For example, if ("Female"jN ) &gt; , then the person is classi ed as a female, or
as a male in case ("Male"jN ) &gt; . Moreover, no inference is made in the range
2 [1:0 ; ] where the gender remains unde ned. For example, when analyzing
a unisex name like Dominique, the result remains unde ned, but adding another
name Gaston, the application interprets the sequence Dominique Gaston as a
male name, or as a female in the case Gabrielle Dominique.</p>
      <p>Person Name Finder Service The Person Name Finder is an API service
for identifying references to people and collecting context around them from
texts. It utilizes the HENKO ontology to identify person names from texts as
a NER task. The Person Name Finder uses the linkage of the family names to
places and vocations to di erentiate between them and person names. In case
the application nds from a text a reference to a single family name and there
are no full names with the same family name in the text, it checks if the name
is linked to either a place or vocation. If the family name has been linked to a
place name, the application returns the place reference to indicate that the name
can also be a place. The same procedure is applied to vocations; if a sentence
starts with a name that is linked to a vocation written with a capital letter in a
beginning of a sentence, the application returns the vocation link. Otherwise, the
application returns only person names with links to the person name ontology.
In addition, the service can identify information around the name such as times
of birth and death, and the gender by utilizing the Gender Identi cation Service.</p>
      <p>The service identi es person names and returns the result set in JSON format.
It has been designed to aid in the extraction of personal information from registry
entries and natural language texts. The result set contains full names and o ers
information related to the name such as location in text, links to HENKO,
and optionally contextual information, such as gender, dates within brackets,
etc. The API and its description22 are available at the SeCo Text Annotation
Service. Currently, the application is being developed and used as a part of
named entity recognition and linking to identify person names from the legal
and biographical texts. It has been able to identify most names and even some
older names, and to enrich them with information such as years within brackets,
and gender.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Evaluation</title>
      <p>This section evaluates the enriching methods for the initial data in Section 2 and
the Gender Identi cation Service from Section 4.
22 http://nlp.ldf.fi/api-documentation/#api-NameFinder</p>
      <p>The use of NLP methods for data enrichment provided satisfactory results.
The identi cation of matronymics and patronymics was calculated for 1000
random samples. The F1-score for identi cation of matronymics was 87:27% and for
patronymics 94:42%. Most frequently encountered issue with identi cation was
the lack of Swedish or Russian given names from which the form is derived from.
The extraction of su xes and particles worked well. The F1-score for a sample
of 1000 names was 92:78% for su xes and 100% for particles. The su x
extraction failed for rarer non-Finnish names because they could not be hyphenated
correctly due to language identi cation or lack of hyphenation support.</p>
      <p>The linking of names succeeded with varying results. Roughly 23 600 names
are linked to Wikidata, and 2500 to DBpedia. The rest of the names could not
be linked because either the database did not include the name or there were
errors in the data. Often older or less popular names could not be found in
either target ontology. Also, some Asian names were linked to several entities
in Wikidata with the same label, e.g. Jin was linked to two Chinese and one
Korean name. The linking of names to topics matched to 785 places and 30
vocations. The success of the linking depended on the quality and coverage of
the target ontology. Names from pre-Christian era could not be linked to places
or vocations because the target ontologies do not contain a historical vocabulary
for the entities.</p>
      <p>
        The Gender Identi cation Service was evaluated using the names of the
relatives extracted from BiographySampo data. It recognized 97:70% of the unique
names leaving out only very rare or foreign names. In the test set, all recognized
genders were inferred correctly [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. In addition to using given names, the gender
can be concluded e.g. by occupation, by known family relations, or by external
contextual information. For example, in the case of AcademySampo all students
starting earlier than in 1870 are male [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] since female students were not allowed.
6
      </p>
    </sec>
    <sec id="sec-6">
      <title>Data Service</title>
      <p>
        The person name ontology is published as Linked Open Data on the Linked Data
Finland (LDF. ) platform [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], adhering to the FAIR principles23. The platform
provides a public SPARQL endpoint24, IRI dereferencing capabilities, including
a generic RDF browsing user interface, and a dataset homepage25 with general
documentation based on the SPARQL Service Description26, containing a
Vocabulary of Interlinked Datasets (VoID) description27 of the dataset. For
humanreadable data model documentation28, we use LODE [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ]: when dereferencing
IRIs of the name ontology's schema, the user is redirected to a page listing the
classes and properties used. The ontology is also published in the ONKI Light
23 https://www.go-fair.org/fair-principles/
24 http://ldf.fi/henko/sparql
25 http://ldf.fi/dataset/henko
26 https://www.w3.org/TR/sparql11-service-description/
27 https://www.w3.org/TR/void/
28 http://ldf.fi/schema/henko/
service29, where it is searchable and browsable using SKOSMOS30, a web-based
SKOS browser. The data is served on the Apache Jena Fuseki triplestore. The
Fuseki runtime and the person name ontology data are built into a Docker
image31 which can be easily rebuilt when there is a need to publish a new version
of the data, by simply updating the data in a Git repository.
7
      </p>
    </sec>
    <sec id="sec-7">
      <title>Conclusions</title>
      <p>This paper presents the person name ontology HENKO that consists of Finnish
person names from the 3rd century to present time. Unlike actor ontologies
and vocabularies such as ULAN and BIO, HENKO concentrates on describing
person names and their features. The ontology is published as linked open data
that connects to AcademySampo, BiographySampo, Norssi Alumni datasets and
semantic portals, Wikidata, DBpedia, YSO places, and AMMO ontologies. Its
unique data model was in uenced by largely used ontologies and vocabularies
such as Wikidata, Schema.org, and DBpedia. Out of these ontologies, Wikidata
has the most extensive model thus far for names; it divides names by gender,
includes etymological information, and has pronunciation instructions. In
addition, the Wikidata ontology di erentiates patronymic and matronymic names. In
contrast, HENKO consists of a large set of Finnish names of which nearly 45%
could be linked to Wikidata. In addition, the HENKO has more information
about the names such as their usage statistics, linguistic information (su xes,
particles), and provenance information. HENKO model can be used as is for
simple patterns consisting of given and family names. In addition, by adding the
modelling for middle names, it can be used for wider range of naming
conventions. Hence, the ontology is a novel resource for di erent applications. It can
also be used as training material for deep learning based NLP applications alike.</p>
      <p>
        The accuracy of extracting particles and su xes was satisfactory. The
minor issues of su x extraction could be solved by identifying and splitting
family names that are compound words with tools such as the Turku dependency
parser [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] or LAS's morphological analyzer. In addition to family names, also
given names can contain su xes that have so far been ignored. They can, e.g.,
indicate the bearer's gender, like in the female Wilhelmiina based on the male
name Wilhelm. The identi cation and extraction of su xes enables data
analysis for the names. For example, in the history of Finnish last names [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ], there
have been periods when it has been popular to change Swedish or Russian names
to Finnish names with su xes such as -la or -nen. When analyzing the
AcademySampo data, we found out that family names with su x -nen start to appear
only after 1830. To analyze the temporal characters of family names with other
su ces remain as future work. Given names [
        <xref ref-type="bibr" rid="ref28">28</xref>
        ] have also been modi ed but by
the clergy keeping the parish registries according to the guidelines of di erent
central governments; for example the name Gregorius has been changed to the
29 http://light.onki.fi/henko/en/
30 http://skosmos.org
31 https://hub.docker.com/r/secoresearch/fuseki/
Finnish name Reijo32. One future research direction for enriching the data could
be to represent there changes of names based on genealogical data and track the
changes and su xes in di erent linked source datasets. This would also aid in
named entity linking (NEL), as the name changes in historical documents could
be understood and references to people could be disambiguated better if
indicated that the person used di erent changed names. Modeling of the changes of
names has been researched earlier, e.g., in the context of biological taxa [
        <xref ref-type="bibr" rid="ref3 ref30">30,3</xref>
        ].
      </p>
      <p>
        The linking of family names to places and vocations enriched the ontology
and added context to names. The Person Name Finder utilizes the added context
to identify possibly ambiguous nouns when it is used to identify names from text.
Unlike typical NEL tools [
        <xref ref-type="bibr" rid="ref23 ref24 ref5">23,24,5</xref>
        ] that concentrate on simply linking entities to
knowledge bases, the application can be utilized to extract names from texts and
enrich them with contextual information. The Person Name Finder application
is still under work, and will be further developed to ease linking to related
actor ontologies. In addition to topical linking, in the future, place name linking
can be used similarly to, e.g., Tuomas Salste's work33 by locating the origin of
names and visualizing them on a map to aid in genealogical research. By using
the extracted su xes, the linking of names to places could be improved and
expanded to names that refer to places but contain a su x that prevents linking
(e.g., Savola referes to Savo without the -la su x).
      </p>
      <p>
        The usage statistics of the names enables the usage of the ontology in the
Gender Identi cation Service. Although the functionality of the service is
straightforward and based on relative trivial statistics, e.g., it does not consider the
cooccurrence of the names and it does not return an estimate for names missing
in the ontology, the results have been feasible in our use cases. Related to our
service, there are commercial projects such as genderize34 and gender-api35 that
also use name vocabularies for decision making. Attempt to infer the gender by
the ending of the name [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] is problematic with Finnish names where, e.g., Jari
and Kari are male names but Sari and Mari female ones. A blog post [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] by
Ellis Brown introduces a project where the gender is inferred from character
sequences in names using a recurrent neural network. Due to the feasible results
for our use cases, we have not implemented similar algorithms for inferring the
gender for names missing from our vocabulary.
      </p>
      <p>Acknowledgments This work is part of the Anoppi project36 funded by
the Ministry of Justice in Finland. Thanks to Aki Hietanen, Saara Packalen,
Tiina Husso, and Oili Salminen of the Ministry of Justice, and Risto Talo, Jari
Linhala, and Arttu Oksanen of Edita Publishing Ltd. for collaboration. Thanks
also to Aleksandra Konovalova from University of Helsinki and Esko Kirjalainen
from The Finnish Digital Agency for insightful discussions. CSC { IT Center for
Science, Finland, provided us with computational resources.
32 https://www.genealogia.fi/nimet/nimi15s.htm
33 https://www.tuomas.salste.net/suku/nimi/
34 https://genderize.io
35 https://gender-api.com
36 https://seco.cs.aalto.fi/projects/anoppi/en/</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bird</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klein</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Loper</surname>
          </string-name>
          , E.:
          <article-title>Natural Language Processing with Python. Analyzing Text with the Natural Language Toolkit</article-title>
          ,
          <source>chap. 6.1</source>
          .1.
          <string-name>
            <given-names>O</given-names>
            <surname>'Reilly Media</surname>
          </string-name>
          , Inc. (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Brown</surname>
          </string-name>
          , E.:
          <article-title>Gender Inference from Character Sequences in Multinational First Names</article-title>
          . https://towardsdatascience.com/ name2gender-introduction-626d89378fb0, accessed:
          <source>2020 Mar 3</source>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Chawuthai</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Takeda</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wuwongse</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jinbo</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>Presenting and Preserving the Change in Taxonomic Knowledge for Linked Data</article-title>
          .
          <source>Semantic Web</source>
          <volume>7</volume>
          (
          <issue>6</issue>
          ),
          <volume>589</volume>
          {
          <fpage>616</fpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Erxleben</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          , Gunther,
          <string-name>
            <surname>M.</surname>
          </string-name>
          , Krotzsch,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Mendez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Vrandecic</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
          </string-name>
          :
          <article-title>Introducing Wikidata to the linked data web</article-title>
          .
          <source>In: International Semantic Web Conference</source>
          . pp.
          <volume>50</volume>
          {
          <fpage>65</fpage>
          . Springer (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Francis-Landau</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Durrett</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klein</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Capturing Semantic Similarity for Entity Linking with Convolutional Neural Networks</article-title>
          .
          <source>arXiv preprint arXiv:1604.00734</source>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Guha</surname>
            ,
            <given-names>R.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brickley</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Macbeth</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          : Schema.
          <article-title>org: Evolution of Structured Data on the Web</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>59</volume>
          (
          <issue>2</issue>
          ),
          <volume>44</volume>
          {
          <fpage>51</fpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Hachey</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Radford</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nothman</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Honnibal</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Curran</surname>
            ,
            <given-names>J.R.</given-names>
          </string-name>
          :
          <article-title>Evaluating entity linking with Wikipedia</article-title>
          .
          <source>Arti cial Intelligence</source>
          <volume>194</volume>
          ,
          <fpage>130</fpage>
          {150 (Jan
          <year>2013</year>
          ). https://doi.org/10.1016/j.artint.
          <year>2012</year>
          .
          <volume>04</volume>
          .005, http://dx.doi.org/10. 1016/j.artint.
          <year>2012</year>
          .
          <volume>04</volume>
          .005
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. Hyvonen, E.,
          <string-name>
            <surname>Tuominen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alonen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Makela, E.:
          <article-title>Linked Data Finland: A 7- star Model and Platform for Publishing and Re-using Linked Datasets</article-title>
          . In: The Semantic Web:
          <article-title>ESWC 2014 Satellite Events</article-title>
          ,
          <source>Revised Selected Papers</source>
          . pp.
          <volume>226</volume>
          {
          <fpage>230</fpage>
          . Springer-Verlag (May
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. Hyvonen, E.,
          <string-name>
            <surname>Leskinen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heino</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tuominen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sirola</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Reassembling and Enriching the Life Stories in Printed Biographical Registers: Norssi High School Alumni on the Semantic Web</article-title>
          .
          <source>In: Proceedings, Language, Technology and Knowledge (LDK</source>
          <year>2017</year>
          ). pp.
          <volume>113</volume>
          {
          <fpage>119</fpage>
          . Springer-Verlag (
          <year>June 2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10. Hyvonen, E.,
          <string-name>
            <surname>Leskinen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tamper</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rantala</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ikkala</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tuominen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Keravuori</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Linked Data { A Paradigm Change for Publishing and Using Biography Collections on the Semantic Web</article-title>
          .
          <source>In: Proceedings of the Third Conference on Biographical Data in a Digital World (BD</source>
          <year>2019</year>
          ) (
          <year>September 2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Joudrey</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Taylor</surname>
          </string-name>
          , A.,
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Introduction to Cataloging and Classi cation</article-title>
          .
          <source>Libraries Unlimited</source>
          ,
          <volume>11</volume>
          <fpage>edn</fpage>
          . (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Kanerva</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ginter</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miekka</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leino</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Salakoski</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Turku Neural Parser Pipeline: An End-to-End System for the CoNLL 2018 Shared Task</article-title>
          .
          <source>In: Proceedings of the CoNLL</source>
          <year>2018</year>
          <article-title>Shared Task: Multilingual Parsing from Raw Text to Universal Dependencies. Association for Computational Linguistics (</article-title>
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Klimek</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Proposing an OntoLex-MMoOn Alignment: Towards an Interconnection of two Linguistic Domain Models</article-title>
          .
          <source>In: LDK Workshops</source>
          . pp.
          <volume>68</volume>
          {
          <issue>73</issue>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Klimek</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arndt</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krause</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arndt</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Creating Linked Data Morphological Language Resources with MMoOn { The Hebrew Morpheme Inventory</article-title>
          .
          <source>In: Proceedings of the Tenth International Conference on Language Resources and Evaluation (LREC'16)</source>
          . pp.
          <volume>892</volume>
          {
          <issue>899</issue>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Koho</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gasbarra</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tuominen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rantala</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jokipii</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          , Hyvonen, E.:
          <article-title>AMMO Ontology of Finnish Historical Occupations</article-title>
          .
          <source>In: Proceedings of the First International Workshop on Open Data and Ontologies for Cultural Heritage (ODOCH'19)</source>
          . vol.
          <volume>2375</volume>
          , pp.
          <volume>91</volume>
          {
          <fpage>96</fpage>
          . CEUR Workshop Proceedings (
          <year>June 2019</year>
          ), vol
          <volume>2375</volume>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Leskinen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , Hyvonen, E.:
          <article-title>Extracting Genealogical Networks of Linked Data from Biographical Texts</article-title>
          .
          <source>In: Proceedings of the 16th Extended Semantic Web Conference (ESWC</source>
          <year>2019</year>
          ), Portoroz, Posters &amp; Demonstrations (
          <year>June 2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Leskinen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , Hyvonen, E.:
          <source>Linked Open Data Service about Historical Finnish Academic People in 1640{1899. In: Proceedings of Digital Humanities in Nordic Countries (DHN</source>
          <year>2020</year>
          ), Riga. CEUR Workshop Proceedings (March
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18. Makela, E.:
          <article-title>Combining a REST lexical analysis web service with SPARQL for mashup semantic annotation from text</article-title>
          .
          <source>In: European Semantic Web Conference</source>
          . pp.
          <volume>424</volume>
          {
          <fpage>428</fpage>
          . Springer (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19. Makela, E.:
          <article-title>LAS: an integrated language analysis tool for multiple languages</article-title>
          .
          <source>The Journal of Open Source Software</source>
          <volume>1</volume>
          (
          <issue>6</issue>
          ) (
          <year>October 2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Malmi</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rasa</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gionis</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>AncestryAI: A Tool for Exploring Computationally Inferred Family Trees</article-title>
          .
          <source>In: Proceedings of the 26th International Conference on World Wide Web Companion</source>
          . pp.
          <volume>257</volume>
          {
          <fpage>261</fpage>
          .
          <string-name>
            <surname>International World Wide Web Conferences Steering Committee</surname>
          </string-name>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>McCrae</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bosque-Gil</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gracia</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Buitelaar</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cimiano</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>The OntoLexLemon model: development and applications</article-title>
          .
          <source>In: Proceedings of eLex 2017 conference</source>
          . pp.
          <volume>19</volume>
          {
          <issue>21</issue>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>McCrae</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chiarcos</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bond</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cimiano</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Declerck</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>De Melo</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gracia</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hellmann</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klimek</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moran</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , et al.: The Open Linguistics Working Group:
          <article-title>Developing the Linguistic Linked Open Data Cloud</article-title>
          .
          <source>In: Proceedings of the Tenth International Conference on Language Resources and Evaluation (LREC'16)</source>
          . pp.
          <volume>2435</volume>
          {
          <issue>2441</issue>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Mendes</surname>
            ,
            <given-names>P.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jakob</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garc</surname>
            a-Silva,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Dbpedia spotlight: shedding light on the web of documents</article-title>
          .
          <source>In: Proceedings of the 7th international conference on semantic systems</source>
          . pp.
          <volume>1</volume>
          {
          <issue>8</issue>
          .
          <string-name>
            <surname>ACM</surname>
          </string-name>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Nguyen</surname>
            ,
            <given-names>D.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ho</surname>
            <given-names>art</given-names>
          </string-name>
          , J.,
          <string-name>
            <surname>Theobald</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weikum</surname>
          </string-name>
          , G.:
          <article-title>AIDA-light: Highthroughput named-entity disambiguation</article-title>
          .
          <source>In: Proceedings of the Workshop on Linked Data on the Web (LDOW</source>
          <year>2014</year>
          )
          <article-title>, co-located with the 23rd</article-title>
          <source>International World Wide Web Conference (WWW</source>
          <year>2014</year>
          ). vol.
          <volume>1184</volume>
          . CEUR Workshop Proceedings (April
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Oksanen</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tamper</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tuominen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hietanen</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , Hyvonen, E.:
          <article-title>Anoppi: A pseudonymization service for Finnish court documents</article-title>
          . In: Araszkiewicz,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Rodr</surname>
          </string-name>
          guez-Doncel, V. (eds.)
          <article-title>Legal Knowledge and Information Systems</article-title>
          .
          <source>JURIX</source>
          <year>2019</year>
          :
          <article-title>The Thirty-second Annual Conference</article-title>
          . pp.
          <volume>251</volume>
          {
          <fpage>254</fpage>
          . IOS Press (
          <year>December 2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Paikkala</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Sukunimet sukututkimuksessa</article-title>
          .
          <source>Sukutieto: Sukutietotekniikka ry:n jasenlehti 14(4)</source>
          (
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Peroni</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shotton</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vitali</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Tools for the Automatic Generation of Ontology Documentation: A Task-Based Evaluation</article-title>
          .
          <source>International journal on Semantic Web and information systems 9(1)</source>
          ,
          <volume>21</volume>
          {
          <fpage>44</fpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Rajasuu</surname>
          </string-name>
          , R.: Kuopiossa,
          <source>Oulussa ja Turussa vuosina 1725{1744 ja</source>
          <year>1825</year>
          {
          <article-title>1844 syntyneiden kastenimet</article-title>
          .
          <source>Ph.D. thesis</source>
          , University of Eastern Finland (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Tamper</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Hyvonen, E.,
          <string-name>
            <surname>Leskinen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Visualizing and Analyzing Networks of Named Entities in Biographical Dictionaries for Digital Humanities Research</article-title>
          .
          <source>In: Proceedings of the 20th International Conference on Computational Linguistics and Intelligent Text Processing (CICling</source>
          <year>2019</year>
          ). Springer-Verlag (
          <year>April 2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Tuominen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Laurenne</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          , Hyvonen, E.:
          <article-title>Biological Names and Taxonomies on the Semantic Web { Managing the Change in Scienti c Conception</article-title>
          .
          <source>In: Proceedings of the 8th Extended Semantic Web Conference (ESWC</source>
          <year>2011</year>
          ). pp.
          <volume>255</volume>
          {
          <fpage>269</fpage>
          .
          <string-name>
            <surname>SpringerVerlag</surname>
          </string-name>
          (
          <year>June 2011</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>