<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Knowledge Base Augmentation using Tabular Data *</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Yoones</forename><forename type="middle">A</forename><surname>Sekhavat</surname></persName>
							<email>yoones.a.s@ualberta.ca</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Alberta</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Francesco</forename><surname>Di Paolo</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Roma Tre University</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Denilson</forename><surname>Barbosa</surname></persName>
							<email>denilson@ualberta.ca</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Alberta</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Paolo</forename><surname>Merialdo</surname></persName>
							<email>merialdo@dia.uniroma3.it</email>
							<affiliation key="aff1">
								<orgName type="institution">Roma Tre University</orgName>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff2">
								<orgName type="institution">Barcelona FC Fabio Cannavaro Italy Juventus Kaka Brazil AC Milan Lionel Messi Argentina Barcelona FC</orgName>
								<address>
									<addrLine>LDOW2014, April 8</addrLine>
									<postCode>2014</postCode>
									<settlement>Seoul</settlement>
									<country>Korea. Ronaldinho Brazil</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Knowledge Base Augmentation using Tabular Data *</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">8AF24740BD4427B233012ADC1F589698</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T19:49+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Large linked data repositories have been built by leveraging semi-structured data in Wikipedia (e.g., DBpedia) and through extracting information from natural language text (e.g., YAGO). However, the Web contains many other vast sources of linked data, such as structured HTML tables and spreadsheets. Often, the semantics in such tables is hidden, preventing one from extracting triples from them directly. This paper describes a probabilistic method that augments an existing knowledge base with facts from tabular data by leveraging a Web text corpus and natural language patterns associated with relations in the knowledge base. A preliminary evaluation shows high potential for this technique in augmenting linked data repositories.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">INTRODUCTION</head><p>The Web is bursting with valuable tabular data that could be leveraged in many applications such as knowledge base population and query answering. For instance, Cafarella et al. report 14.1 billion HTML tables in English documents in Googles's main index <ref type="bibr" target="#b4">[4]</ref> and over 400,000 Excel spreadsheets in the Clueweb09 1 crawl <ref type="bibr" target="#b5">[5]</ref>. Tapping into these semistructured information sources is difficult, however, and often they end up being treated no differently than plain text documents. What is worse, state-of-the-art text-based information extraction systems fail on such tables, as they require full sentences to yield good results.</p><p>Tables have inherent semantics which are often implicit or only given in the pages that contain them. Consider the example in Figure <ref type="figure" target="#fig_0">1</ref>, which is a snapshot of a table in Wikipedia. It may not obvious from the table that it is about winners of FIFA's World Player of the Year Award. Nevertheless, it should be noted that the fact that someone put those literals together in the same rows indicates that there are relationships between them. In this case, we know that Ronaldinho was born in Brazil and played for Barcelona. Moreover, the same relationships apply to all rows: Cannavaro was born in Italy and played for Juventus. In fact, we can say that the relations was born in and played for are defined over the columns (1st and 2nd, and 1st and 3rd, respectively).</p><p>A general approach for understanding such tables with the help of linked open data web <ref type="bibr" target="#b2">[2]</ref> would be to <ref type="bibr" target="#b1">(1)</ref> link the values in each cell to known entities in a linked data knowledge base (e.g., YAGO <ref type="bibr" target="#b14">[14]</ref> and Freebase <ref type="bibr" target="#b3">[3]</ref>), and (2) identify relations between the linked values. The best-case-scenario for this approach would be when all entities are linked to the same knowledge base, and a relation already exists between them (this is the approach in <ref type="bibr" target="#b8">[8]</ref>). However, there are other situations. For example, it could be that the entities exist in different, unlinked, knowledge bases, or that some of the entities are not linked to anything yet. Tackling such cases would provide new triples, thus augmenting the linked open data web with new facts. This paper focuses on the problem of identifying plausible relations between pairs of entities that appear in the same row of a table. Our main assumption is that if someone went to the trouble of juxtaposing these entities on the same file, then there must be a relation between them. Moreover, we seek to augment an existing repository with new instances of relations already defined. In other words, the list of possible relations is part of the input. We also assume the entities can be resolved and linked to a linked open data repository or knowledge base. However, unlike previous works (e.g., <ref type="bibr" target="#b8">[8]</ref>), our method does not require that.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Overview.</head><p>As an example, assume our input table has only columns 1 and 3 in Figure <ref type="figure" target="#fig_0">1</ref>, and assume we have two candidate relations: plays-for and lives-in. We start from a list of textual patterns that are associated with each relation; such patterns are detected by automatic methods for building knowledge bases from natural language<ref type="foot" target="#foot_0">2</ref> . For example, patterns for the relation plays-for could be "scored for" and "signed contract with". In practice, thousands of patterns are associated with a single relation; conversely, the same pattern may be associated with multiple relations. Thus, we build a probabilistic model to estimate the posterior probability of a relation, given a set of text patterns observed. To make a prediction for a given pair of entities, we: (1) collect all sentences containing both entities from a large text corpus; <ref type="bibr" target="#b2">(2)</ref> extract the text in between them;</p><p>(3) match those texts against the list of patterns; and (4) estimate the posterior probability of all candidate relations. Paper Outline. Section 2 illustrates our model to extract triples from tabular data. Section 3 discusses our first implementation of the model, and Section 4 reports the results of experiments on this first implementation. Section 5 presents related work, and Section 6 concludes the paper and presents ideas to improve our model.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">TRIPLE EXTRACTION</head><p>In general terms, the problem we address is as follows:</p><p>Given a table T , with n rows and k columns, whose cells contain mentions to entities, and a set R = {r1, . . . , rm} of relations of interest, we aim to produce all triples ti[x], rj, ti[y] ∀ti ∈ T , rj ∈ R, where ti[x] denotes the value of column x in row i.</p><p>Furthermore, we seek to assign relation rj to pairs of columns in T , in the sense that the predicate rj holds for all rows of T . The problem boils down to the case of an input table with just two columns x and y, and, without loss of generality, we address this case here.</p><p>Understanding semantic relations between entities using text corpora is a challenging task because a relation can be expressed with different textual (surface) forms. For example, the relation plays-for can be inferred from sentences with the patterns "scored for" and "signed contract with". On the other hand, a pattern may express more than one relation. For example, the pattern "played in" may represent relations plays-for and performed-at (e.g., "Pink Floyd played in Pompeii").</p><p>Another challenge, which has been the subject of substantial work recently, is entity linking. For example, "Barcelona" may represent the football club or the city. Evidently, the choice of entity linking approach will have an impact on the quality of the triples produced by a method like ours. To avoid this factor in our study of the relation assignment problem we use exact matching to "link" the entities. In effect, this is akin to assuming the entities are already linked.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">Relation between a Pair of Entities</head><p>We start with determining whether a relation r applies to two entities. In the absence of further information, a reasonable approach is to search the (textual) Web for all sentences connecting the entities and determine whether r follows from those sentences. While textual entailment and other reasoning methods could be used for this purpose, we turn this into a probabilistic inference as follows. We start from a known set of textual patterns p1, . . . , p k that are commonly associated with relation r; thus giving us prior probabilities for each pattern expressing the relation. To determine if entities e1 and e2 belong in relation r, we search the corpus for all sentences containing both e1 and e2, extract all words in between them, and match those words against the list of patterns. We can use Bayesian inference to compute the posterior probability of r given the observed patterns.</p><p>In this model, relation r is a categorical class variable whose domain is R, and the patterns p1, ..., pn are binary evidence variables, representing patterns observed between entities in the text corpus. The model is thus: P r(r|p1, ..., p k ) = P r(r)P r(p1, ..., p k |r) P r(p1, ..., p k )</p><p>Relations maximizing P r(r|p1, ..., p k ) are the most probable relations for the entities (given the corpus used). A last component in the model is a threshold to filter low-confidence predictions.</p><p>We assume evidence variables {p1, ..., pn} are conditionally independent, which is reasonable since the probability that pattern pi represents a relation does not depend on the probability that another pattern pj also represents that relation. Given this assumption and using the Chain rule, we have:</p><formula xml:id="formula_1">P r(r|p1, ..., p k ) = P r(r) k i=1 P r(pi|r) P r(p1, ..., p k ) (2)</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Relation between Two Lists of Entities</head><p>Consider now the case of a table with n rows (i.e. a list of n entity pairs). There are two main approaches, illustrated in Figure <ref type="figure" target="#fig_1">2</ref>: we can find one relation assignment for each row and compute an aggregate from all these assignments, or we can observe all text patterns for all rows at once and obtain a global assignment. We discuss each next.</p><p>Rank Aggregation. In this approach, we first obtain a ranking of all relations in R sorted in decreasing likelihood according to the model above, for each pair of entities in the table. Next, we combine these ranked lists to find a single best relation for all entity pairs.</p><p>Rank aggregation <ref type="bibr">[7]</ref> is a well-studied problem: given n ranked lists l1, ..., ln, and a distance measure d, the problem is to find a list l such that n i=1 d(l, li) is minimized. Among different distance measures to aggregate ranking lists, we use Spearman's Footrule (SP) and Kendall's tau (KE) which were shown to outperform other approaches <ref type="bibr">[7]</ref>. Kendall's tau distance between two permutations of a list is the sum of the number of pairs from the list which are not in the same order in these two permutations. This distance is also known as the number of exchanges needed in a bubble sort to convert one permutation to another. On the other hand, Spearman's Footrule distance is the sum of the distances between positions of each item in two different permutations. We also employ a simple average score method to aggregate ranking lists called Mean Ranking (MR), which works as follows: given a sorted (descending) list of probabilities P r(r|p1, ..., p k ) generated for each pair xi, yi , and m possible relations in the knowledge base, we assign a score sci(r) = m − pos(r), where pos(r) is the position of relation r in this sorted list.</p><p>Global Ranking. Another approach is to feed all patterns for all entity pairs in the relation as evidence to the probabilistic model. In this Global Ranking (GR) approach, all observed patterns for all entity pairs simultaneously contribute to selection of the most probable relation.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">IMPLEMENTATION</head><p>This section describes one instantiation of the probabilistic model developed in the previous section, using off-the-shelf, real-world knowledge bases and text corpora.</p><p>Data. We use YAGO <ref type="bibr" target="#b14">[14]</ref> and PATTY <ref type="bibr" target="#b12">[12]</ref> to obtain relations and patterns. YAGO is a popular knowledge base with about 10 million entities and 120 million facts, and PATTY, developed by the same research group, associates 22,779 patterns mined from New York Times articles and Wikipedia with 25 relations. Of those, 24 exist in YAGO and were used here. Our text corpus is the NELL Subject-Verb-Object triple corpus <ref type="bibr" target="#b15">[15]</ref>, with about 604 million triples As mentioned before, we link entities mentioned in the tables to those in the text corpus with exact string matching. That is, given entities e1 and e2 in a table row, we find all triples in the NELL corpus which have e1 as the subject and e2 as the object. Similarly, we match the verbs of the resulting triples against the PATTY patterns (to obtain the observations).</p><p>In effect, our system uses the "intersection" of PATTY patterns and NELL triples, consisting of 4,357 unique patterns and 108,699,400 triples. The YAGO relation has-academicadvisor was discarded as none of its patterns are found in the NELL corpus. Table <ref type="table" target="#tab_0">1</ref> shows the relations used and the number of patterns in each of them. Note the wide variation in the number of patterns per relation.</p><p>Estimating Prior Probabilities. Recall Equation <ref type="formula">2</ref>. We estimate the prior probability of each of the 24 relations as P r(r)=|r|/ r i ∈R (|ri|), where |r| is the number of instances of relation r, and R is the set of all relations in YAGO. As for P r(p|r), the prior probability that pattern p occurs among instances of relation r, we use the associations between YAGO relations and textual patterns in PATTY: P r(p|r) = |p|/ p i ∈P T (r) |pi|, where P T (r) is the set of patterns associated with r. To avoid zero probabilities, we use the add-one Laplace smoothing technique.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">EXPERIMENTAL EVALUATION</head><p>Since we do not query YAGO to make predictions, we use some of its facts to build a ground-truth to test the accuracy of our model. We extracted facts from YAGO relations where both entities can be matched exactly in the NELL corpus. The number of facts from YAGO that can be found from NELL triples using exact matching varies across relations. The lower bound was 25 facts for relation is-knownfor. For the other relations, we picked several random samples with 25 pairs and tested each separately. The difference in accuracy was negligible, so we used 25 facts per relation.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Effectiveness.</head><p>We performed experiments to evaluate the effectiveness of three different rank aggregation techniques (i.e., Spearman's Footrule (SP), Kendall's tau (KE), and Mean Ranking (MR)) as well as the Global Ranking approach (GR). The ranking of the correct relation generated by the system is considered as a measure of success to annotate that relation. The best result is achieved when the correct relation appears at the top of the ranked list for the facts in that relation in the ground-truth. Table <ref type="table" target="#tab_1">2</ref> shows the number of relations ranked the top 3 positions, as well as anywhere above the 3rd place.</p><p>As one can see, GR outperforms the rank aggregation techniques in identifying correct relations. Among the rank aggregation techniques, MR works slightly better than SP and KE in this test. However, there is no statistical significance in the differences between the results of rank aggregation techniques based on analysis of variance. Another observation is that the number of PATTY patterns has an effect on the accuracy, and this effect is more pronounced for the ranking aggregation methods. As shown in Table <ref type="table" target="#tab_0">1</ref>, relations associated with fewer patterns are less likely to be identified correctly by rank aggregation techniques. We argue this is due to lack of sufficient evidence (patterns) for each pair. It follows that rank aggregation techniques require more evidence in order to infer correct relations. On the other hand, the GR performs better for relations associated with fewer patterns. This happens because it is more likely that many relevant patterns appear in the union of patterns of all pairs compared to individual entity pairs.</p><p>We also filtered out relations with 200 or less patterns in our corpus, recomputed their prior probabilities, and reexecuted the experiments on the same dataset for them. Table <ref type="table" target="#tab_2">3</ref> shows the results of this experiment. Although MR performed slightly better than the other techniques, a statistical test reveals that the differences are not significant.</p><p>What is important to note is that, as expected, filtering out less popular relations leads to higher overall accuracy. Ap-plications using our technique can exploit this trade-off to set the appropriate threshold.</p><p>Performance. For efficiency reasons, we index patterns using a suffix tree in memory. The average execution times in milliseconds for processing a pair of entities (taken over 20 executions) are: 1688 for SP, 1868 for KE; 1729.4 for MR; and 1719 for GR. As one can see, there are no considerable differences among the methods. In fact, our observations are that the majority of the time is spent on matching the entities against the NELL corpus.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">Towards Knowledge Augmentation</head><p>The ultimate goal of our technique is knowledge augmentation by generating new instances of relations from tabular data that are not already in the knowledge base. We performed preliminary experiments to assess if our system could accomplish this goal.</p><p>Our first test was with a spreadsheet including song data available at www.aardvarkdjservices.co.uk (a website specialized in music services). We looked at 48 singer, song pairs from 2 albums, with 24 songs from Elvis Presley, and 24 songs from Frank Sinatra. Every approach returned created as the best relation between those entities. We manually verified the 48 facts in this case, and found that only 31 were already in YAGO. In another experiment, we used a spreadsheet with data about NBA players extracted from wwww.espn.go.com, and tested our system with 100 player, team pairs. YAGO had 92 of these pairs in the is-affiliatedto relation. Every configuration of our system identified all 100 pairs as instances of the plays-for relation, which, one can argue, is a suitable and more specific relation for these entities.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">RELATED WORK</head><p>A lot of work has been done towards understanding tables within text or online. Some have attempted to exploit column headers to identify relations between two columns (e.g., <ref type="bibr" target="#b6">[6]</ref>), which is akin to schema-based data integration. We make no assumption about the existence of this information in our approach as this information may not be available for all tables, making our method more similar to an instance-based data integration approach.</p><p>A probabilistic model is proposed in <ref type="bibr" target="#b17">[16]</ref> to associate class labels with columns and identify relations between entity columns and the rest of columns. Recently, the joint inference technique is used to simultaneously annotate table cells, table columns and relations between columns. In <ref type="bibr" target="#b8">[8,</ref><ref type="bibr" target="#b10">10]</ref>, graphical models are employed to annotate column headers, table cells, and relations between columns. Our work is similar, to some extent, to <ref type="bibr" target="#b11">[11]</ref> in which Wikipedia's tables are used to generate new triples using DBpedia as a knowledge base. Unlike our method, these techniques require linking entities to one or more linked open data repositories.</p><p>The problem has also been considered in terms of extracting schema for tabular data. In <ref type="bibr" target="#b5">[5]</ref>, an extraction system is proposed to convert data stored in spreadsheets into relational tuples. In <ref type="bibr" target="#b1">[1]</ref>, a set of row classes representing common features of individual rows in a table is identified. Then, Conditional Random Fields techniques are used to generate a sequence of row labels.</p><p>Our work is also related to relation extraction techniques from text corpora. In supervised learning (e.g., <ref type="bibr" target="#b19">[18]</ref>), manually labelled relations are used to train a model for labeling relations. On the other hand, in unsupervised approaches (e.g., <ref type="bibr" target="#b13">[13]</ref>), strings between entities in a text corpus are clustered and then simplified to generate relations. In <ref type="bibr" target="#b9">[9]</ref>, the classifier is trained using textual features of sentences between known entities in Freebase. This technique generates instances of new relations, while our technique generates instances of relations linked to exiting relations in linked open data repositories.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">CONCLUSION</head><p>In this paper, we described a probabilistic approach for augmenting linked open data repositories using tabular data, thus tapping into these under-explored sources of valuable information. Unlike prior methods that focus on natural language understanding to determine whether two named entities are even related, we start from the (reasonable) assumption that all entities in the same row of a table are related by construction. Unlike previous methods that attempt to understand tabular data, we take a more pragmatic and effective stance: we label pairs of columns in the table with relations coming from an established knowledge base. By doing so, all facts we extract can be interpreted in the same way as those in the knowledge base.</p><p>We described a first implementation of our model using linked open data resources-YAGO, PATTY and NELL-and showed experimentally that the approach is effective, despite the limitations in the way we match entities. We also showed that it rather easy to find new knowledge with our model. Yet, we have only sketched a research direction rich in opportunities to improve knowledge building and linking in our opinion. There are some limitations that we aim to address in future work. Instead of a limited number of YAGO relations, we aim to use a wide range of relations (e.g., those in Freebase). Moreover, we can increase recall by using proper entity linking techniques such as those in <ref type="bibr" target="#b18">[17]</ref>.</p><p>Another interesting line of future work would be to estimate how many new triples could be extracted from tabular data on the entire Web, and how accurate they could be. To do so, one needs a systematic approach and some machinery to automatically check if the new facts already exists in the knowledge base, as well as whether or not these facts are accurate. Different notions of accuracy apply here. For example, it may be that the new facts contradict existing knowledge, or it could be that they are expressed at a different granularity, as was the case for our experiment with NBA players. One could also use both quantitative and qualitative metrics to chart which websites provide the best data.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Example tabular data.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Rank Aggregation approach vs. Global Ranking.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1 :</head><label>1</label><figDesc>Number of PATTY patterns and ranked obtained by each strategy, for each relation. Aindicates the relation has been incorrectly ranked 4th or lower by the method</figDesc><table><row><cell>Relation</cell><cell>Patterns</cell><cell cols="4">SP KE MR GR</cell></row><row><cell>ismarriedto</cell><cell>1274</cell><cell>1</cell><cell>1</cell><cell>1</cell><cell>1</cell></row><row><cell>created</cell><cell>1148</cell><cell>1</cell><cell>1</cell><cell>1</cell><cell>1</cell></row><row><cell>haschild</cell><cell>1090</cell><cell>-</cell><cell>-</cell><cell>-</cell><cell>3</cell></row><row><cell>influences</cell><cell>694</cell><cell>1</cell><cell>1</cell><cell>2</cell><cell>-</cell></row><row><cell>actedin</cell><cell>624</cell><cell>2</cell><cell>2</cell><cell>1</cell><cell>1</cell></row><row><cell>graduatedfrom</cell><cell>472</cell><cell>1</cell><cell>1</cell><cell>1</cell><cell>1</cell></row><row><cell>isknownfor</cell><cell>452</cell><cell>-</cell><cell>-</cell><cell>-</cell><cell>-</cell></row><row><cell>worksat</cell><cell>447</cell><cell>-</cell><cell>-</cell><cell>1</cell><cell>1</cell></row><row><cell>holdspoliticalposition</cell><cell>417</cell><cell>-</cell><cell>3</cell><cell>1</cell><cell>1</cell></row><row><cell>directed</cell><cell>400</cell><cell>2</cell><cell>-</cell><cell>2</cell><cell>2</cell></row><row><cell>playsfor</cell><cell>354</cell><cell>1</cell><cell>1</cell><cell>1</cell><cell>1</cell></row><row><cell>diedin</cell><cell>335</cell><cell>3</cell><cell>-</cell><cell>1</cell><cell>2</cell></row><row><cell>wasbornin</cell><cell>273</cell><cell>-</cell><cell>-</cell><cell>1</cell><cell>1</cell></row><row><cell>islocatedin</cell><cell>249</cell><cell>-</cell><cell>3</cell><cell>-</cell><cell>-</cell></row><row><cell>livesin</cell><cell>200</cell><cell>-</cell><cell>-</cell><cell>-</cell><cell>-</cell></row><row><cell>isleaderof</cell><cell>156</cell><cell>-</cell><cell>-</cell><cell>-</cell><cell>-</cell></row><row><cell>iscitizenof</cell><cell>121</cell><cell>1</cell><cell>1</cell><cell>-</cell><cell>-</cell></row><row><cell>haswonprize</cell><cell>81</cell><cell>-</cell><cell>-</cell><cell>3</cell><cell>1</cell></row><row><cell>dealswith</cell><cell>59</cell><cell>-</cell><cell>-</cell><cell>-</cell><cell>1</cell></row><row><cell>ispoliticianof</cell><cell>49</cell><cell>1</cell><cell>-</cell><cell>-</cell><cell>1</cell></row><row><cell>participatedin</cell><cell>33</cell><cell>1</cell><cell>1</cell><cell>2</cell><cell>2</cell></row><row><cell>happenedin</cell><cell>12</cell><cell>2</cell><cell>1</cell><cell>-</cell><cell>1</cell></row><row><cell>hascapital</cell><cell>1</cell><cell>2</cell><cell>1</cell><cell>-</cell><cell>-</cell></row></table><note>extracted via dependency parsing on the ClueWeb09 dataset (Clueweb09 is a Web crawl with about 1 billion web pages in ten different languages).</note></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 2 :</head><label>2</label><figDesc>Results of rankings on 23 YAGO relations</figDesc><table><row><cell></cell><cell cols="4">Rank Aggregation Global Ranking</cell></row><row><cell></cell><cell cols="2">SP KE</cell><cell>MR</cell><cell>GR</cell></row><row><cell>Ranked First</cell><cell>8</cell><cell>9</cell><cell>9</cell><cell>12</cell></row><row><cell>Ranked Second</cell><cell>4</cell><cell>1</cell><cell>3</cell><cell>3</cell></row><row><cell>Ranked Third</cell><cell>1</cell><cell>2</cell><cell>1</cell><cell>1</cell></row><row><cell>Ranked &gt; 3</cell><cell>10</cell><cell>11</cell><cell>10</cell><cell>7</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>Table 3 :</head><label>3</label><figDesc>Results of rankings on filtered relations</figDesc><table><row><cell></cell><cell cols="4">Rank Aggregation Global Ranking</cell></row><row><cell></cell><cell cols="2">SP KE</cell><cell>MR</cell><cell>GR</cell></row><row><cell>Ranked First</cell><cell>9</cell><cell>7</cell><cell>9</cell><cell>8</cell></row><row><cell>Ranked Second</cell><cell>1</cell><cell>3</cell><cell>2</cell><cell>2</cell></row><row><cell>Ranked Third</cell><cell>2</cell><cell>1</cell><cell>2</cell><cell>3</cell></row><row><cell>Ranked &gt; 3</cell><cell>2</cell><cell>3</cell><cell>1</cell><cell>1</cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_0">We use the patterns in the PATTY system<ref type="bibr" target="#b12">[12]</ref>.</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgements.</head><p>This work was supported in part by grants from the Natural Sciences and Egineering Reseach Council of Canada and the IBM Alberta Centre for Advanced Studies.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title/>
		<author>
			<persName><surname>References</surname></persName>
		</author>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Schema extraction for tabular data on the web</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">D</forename><surname>Adelfio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Samet</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Proc. VLDB Endow</title>
		<imprint>
			<biblScope unit="volume">6</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="421" to="432" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Linked data-the story so far</title>
		<author>
			<persName><forename type="first">C</forename><surname>Bizer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Heath</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Berners-Lee</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Int. J. Sem. Web Inf. Sys</title>
		<imprint>
			<biblScope unit="volume">5</biblScope>
			<biblScope unit="issue">3</biblScope>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Freebase: A collaboratively created graph database for structuring human knowledge</title>
		<author>
			<persName><forename type="first">K</forename><surname>Bollacker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Evans</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Paritosh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Sturge</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Taylor</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">SIGMOD&apos;08 Conf. Proc</title>
				<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Webtables: Exploring the power of tables on the web</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">J</forename><surname>Cafarella</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Halevy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">Z</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Zhang</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. VLDB Endow</title>
				<meeting>VLDB Endow</meeting>
		<imprint>
			<date type="published" when="2008">2008</date>
			<biblScope unit="volume">1</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Automatic web spreadsheet data extraction</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Cafarella</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">SSW&apos;13 Conf. Proc</title>
				<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Data-gov wiki: Towards linking government data</title>
		<author>
			<persName><forename type="first">L</forename><surname>Ding</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Difranzo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Graves</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Michaelis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">L</forename><surname>Mcguinness</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hendler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">AAAI Spring Symp.: Linked data meets AI</title>
				<imprint>
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Comparing top k lists</title>
		<author>
			<persName><forename type="first">R</forename><surname>Fagin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Kumar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Sivakumar</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">SODA&apos;03 Conf. Proc</title>
				<imprint>
			<date type="published" when="2003">2003</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Annotating and searching web tables using entities, types and relationships</title>
		<author>
			<persName><forename type="first">G</forename><surname>Limaye</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Sarawagi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Chakrabarti</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. VLDB Endow</title>
				<meeting>VLDB Endow</meeting>
		<imprint>
			<date type="published" when="2010">2010</date>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="page" from="1338" to="1347" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Distant supervision for relation extraction without labeled data</title>
		<author>
			<persName><forename type="first">M</forename><surname>Mintz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Bills</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Snow</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Jurafsky</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ACL&apos;09 Conf. Proc</title>
				<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Semantic Message Passing for Generating Linked Data from Tables</title>
		<author>
			<persName><forename type="first">V</forename><surname>Mulwad</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Finin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Joshi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ISWC&apos;13 Conf. Proc</title>
				<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Triplifying wikipedia&apos;s tables</title>
		<author>
			<persName><forename type="first">E</forename><surname>Munoz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Hogan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Mileo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">LD4IE&apos;13 Workshop Proceedings, ISWC. CEUR</title>
				<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Patty: A taxonomy of relational patterns with semantic types</title>
		<author>
			<persName><forename type="first">N</forename><surname>Nakashole</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Weikum</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Suchanek</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">EMNLP-CoNLL&apos;12 Conf. Proc</title>
				<imprint>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Preemptive information extraction using unrestricted relation discovery</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Shinyama</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Sekine</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">HLT-NAACL&apos;06 Conf. Proc</title>
				<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Yago: A core of semantic knowledge</title>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">M</forename><surname>Suchanek</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Kasneci</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Weikum</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">WWW&apos;07 Conf. Proc</title>
				<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Acquiring temporal constraints between relations</title>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">P</forename><surname>Talukdar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Wijaya</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Mitchell</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CIKM&apos;12</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<title level="m">Conf. Proc</title>
				<imprint>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Recovering semantics of tables on the web</title>
		<author>
			<persName><forename type="first">P</forename><surname>Venetis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Halevy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Madhavan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Paşca</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Shen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Miao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Wu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Proc. VLDB Endow</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="issue">9</biblScope>
			<biblScope unit="page" from="528" to="538" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">Aida: An online tool for accurate disambiguation of named entities in text and tables</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Yosef</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hoffart</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Bordino</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Spaniol</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Weikum</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Proc. VLDB Endow</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="issue">12</biblScope>
			<biblScope unit="page" from="1450" to="1453" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">Tree Kernel-Based relation extraction with Context-Sensitive structured parse tree information</title>
		<author>
			<persName><forename type="first">G</forename><surname>Zhou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Ji</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Q</forename><surname>Zhu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">EMNLP-CoNLL&apos;07 Conf. Proc</title>
				<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
