Learning Semantic Annotations for Tabular Data

05/30/2019 ∙ by Jiaoyan Chen, et al. ∙ 0

The usefulness of tabular data such as web tables critically depends on understanding their semantics. This study focuses on column type prediction for tables without any meta data. Unlike traditional lexical matching-based methods, we propose a deep prediction model that can fully exploit a table's contextual semantics, including table locality features learned by a Hybrid Neural Network (HNN), and inter-column semantics features learned by a knowledge base (KB) lookup and query answering algorithm.It exhibits good performance not only on individual table sets, but also when transferring from one table set to another.

READ FULL TEXT VIEW PDF
POST COMMENT

Comments

There are no comments yet.

Authors

page 1

page 2

page 3

page 4

This week in AI

Get the week's most popular data science and artificial intelligence research sent straight to your inbox every Saturday.

1 Introduction

Tabular data such as web tables and legacy databases are a rich and rapidly expanding resource. They often contain high value data, but may be hard to use due to meta data being missing, incomplete or obfuscated. Gaining an understanding of their meaning is thus of critical importance. One prominent solution, which is often referred to as semantic table annotation, is to exploit the semantics of a widely recognized knowledge base (KB) by linking table components, such as columns and cells, to KB components, such as classes (categories), entities (elements) and properties (relations). It can be widely applied in KB population [Ritze et al.2016], search engines [Cafarella et al.2008, Cafarella et al.2018], automatic data analysis [Thirumuruganathan et al.2018, Chu et al.2015] and so on.

Semantic table annotation has been extensively studied, especially for web tables [Cafarella et al.2018]. Traditional methods are mostly based on lexical matching by name, with annotation modeled as tasks such as matching cells to entities, columns to classes, inter-column relations to properties and so on [Limaye et al.2010]. Other methods, including probabilistic graphical models [Bhagavatula et al.2015] and iterative algorithms [Ritze et al.2015], have been developed to explore the correlation between different matching tasks for disambiguation. However, most of them rely on table metadata such as column names to jointly model multiple matching tasks, while lexical matching itself fails to capture the contextual semantics of a name.

Recently some studies have explored the use of deep learning in semantic table annotation. For example

[Luo et al.2018] learns cell contextual features to predict its corresponding KB entity (cf. Section 4). These works illustrate the benefit of deep learning in modeling contextual semantics of tables, but they still have limitations: (i) some tasks, such as column type annotation, have not been fully investigated; (ii) some contextual semantics, such as inter-column relations, have not been fully explored; and (iii) the transferability (generalization) of the learned model has not been evaluated.

In this study, we focus on semantic type (i.e., class) prediction for columns that are composed of phrases (i.e., entity mentions). For example, a column composed of “Google”, “Amazon” and “Apple Inc.” can be annotated by the class Company

. To this end, we first develop a Hybrid Neural Network (HNN) to model the contextual semantics of a column. It embeds the phrase within a cell with a bidirectional Recurrent Neural Network and an attention layer (Att-BiRNN), and learns

(i) column features (i.e., intra-column cell correlation) and (ii)

row features (i.e., intra-row cell correlation) with a Convolutional Neural Network (CNN).

The arbitrary relative position of columns makes it difficult for the neural network to learn general row features. Thus we extend the row features with property features, which indicate potential relations between columns and provide discriminative predictive information. For example, given a column composed of “Animal Farm”, “The Goldfather” and “Brokeback Mountain”, together with a column of person names, the potential relation director indicates the first column is more likely to be of type Film, while the relation author suggests Book

as probable type. To extract such property features, a novel KB lookup and reasoning algorithm was developed.

In summary, this study contributes a new column type prediction method combing HNN for feature learning and KB lookup and reasoning for feature extraction. We evaluate our technique using the DBpedia KB and three table sets: T2Dv2 from the general Web, Limaye and Efthymiou from the Wikipedia encyclopedia. As well as testing single table sets, the evaluation specially considers the generalization (transferability) of the prediction model from one table set to another. The evaluation suggests that our method is effective and that its overall accuracy is higher than the state-of-the-art in most cases.

2 Methodology

2.1 Problem Statement

We assume a table is composed of cells organized by columns and rows, without any metadata like column names. The input is a table with a target column whose type is to be predicted. The column includes ordered cells, each of which is a sequence of words (text phrase), known as an entity mention. A column composed of entity mentions is also known as an entity column. Other columns in the input table are called surrounding columns. We assume a fixed set of candidate classes that are disjoint with each other are given, denoted as . The problem is assigning a real value score to each candidate class so that the correct class (type) of the target column has the highest score.

The input of our method is modeled as a fixed structure table called a micro table, denoted as . It has one target column with a fixed number of cells, denoted as , and a fixed number of surrounding columns, denoted as . The first cell of the target column is known as the micro table’s main cell.

In training, we assume labeled micro tables (samples) are extracted from labeled entity columns by (i) sliding a window from the first row to the last with the step of one cell and (ii) selecting surrounding columns from the left to the right. A function (model) is learned, where

represents the output vector. In predicting the type of a target column with size

, micro tables are first extracted and predicted by the trained model . Their output vectors are then averaged as the final score vector to the target column: . The remainder of this section presents our model , while some of its training details are presented in Section 3.

2.2 HNN Architecture

Our HNN mainly includes an attentive BiRNN for cell embedding, and a customized convolutional (Conv) layer for table locality feature learning, as shown in Figure 1.

Figure 1: A brief view of the HNN architecture.

2.2.1 Cell Embedding

We use an RNN with Gated Recurrent Unit (GRU)

[Bhagavatula et al.2015] to embed the word sequence of each cell (). It uses a reset gate to control the contribution of past state (word), and an update gate to balance the contributions of past information and new information. The hidden state at position is computed as

(1)

where denotes the Hadamard product, represents the past state, is a state computed with new sequence information. , and are updated as

(2)

Assume the cell phrase length is fixed to

by cropping and padding, and each cell phrase is represented as

where denotes the vector of the word at position . In BiRNN, both forward hidden states (, ) and backward hidden states (, ) are calculated. The embedding of the word at position , denoted as , is the concatenation of and .

The embedding of a cell phrase is composed of the BiRNN embeddings of its words. Inspired by [Yang et al.2016], we assume different words are differently informative towards a prediction task, and an attention layer is thus stacked. Given a phrase with BiRNN word embedding (), the attention layer output is , where is the normalized weight of the word at position and is calculated as

(3)

The dimension of cell embedding is denoted as ; represents the informative degree of all the words in training.

Given a micro table, the cells of the target column and the cells of its surrounding entity columns are embedded by the above Att-BiRNN; the cells of the surrounding real value columns are transformed into a vector of dimension by zero padding; the cells of the surrounding date columns are first parsed with integers of year, month and day, and then transformed into a vector of dimension by concatenating the integers and zero padding.

One column is embedded into a matrix of size by stacking vectors of its cells. For convenience, we also use the annotation of a column to denote its embedded matrix (i.e., for the target column,

for a surrounding column). One micro table is embedded into a tensor of size

by stacking matrices of its columns, denoted as .

2.2.2 Column Features and Row Features

One Conv layer is stacked after Att-BiRNN, including (i) Conv filters over the target column for column feature learning, denoted as , and (ii) Conv filters over the row of the main cell for row feature learning, denoted as .

Each filter over the column has the size of , where , . Given the matrix of the target column , the filter computes the column features as

(4)

where denotes the Conv operation,

denotes an activation function like ReLu and

denotes the biases.

Each filter over the row has the size of , where , . Given the tensor of a micro table, the filter computes the row features as

(5)

where denotes the first cell of surrounding column , denotes the biases. It models the correlation between the target column and its surrounding columns.

Inspired by some successful CNN architectures with one Conv layer (e.g., [Kim2014]

for text classification), a max pooling layer is stacked after the Conv layer to extract salient signals and regularize the network. Thus the column filter

finally computes the output as

(6)

where denotes a vector’s maximum value, denotes the number of features to be learned for each filter. For the row filter , with the number of features , the output, denoted as is calculated in the same way as (6).

The max pooling layer concatenates , and , as the output, denoted as . , , and are hyper parameters about the HNN architecture.

A fully connected (FC) layer is then stacked for modeling the nonlinear relationship. It calculates the output as

(7)

where denotes matrix multiplication, and

denote weights and biases of the FC layer. Finally, a softmax layer is stacked to calculate the output score for each class:

(8)

where .

2.3 Property Features

Property features are used to represent the potential relations between the target column and its surrounding columns. We first introduce some KB background and then present how property features are extracted and incorporated.

2.3.1 RDF-based Knowledge Base

The KB in this study follows Semantic Web standards including RDF (Resource Description Framework), RDF Schema, OWL (Web Ontology Language) and SPARQL [Domingue et al.2011]. One KB is composed of a TBox (terminology) and an ABox (assertions). The TBox, often using RDF Schema, contains constructors for the definition of class, class relations (e.g., rdfs:subClassOf for the descendent relation), property, property domain and range, etc. It can also use more expressive languages such as OWL with more powerful constructs such as relation composition. The ABox contains entities, each of which is represented by an URI (Uniform Resource Identifier), and RDF triples , where represents a subject (an entity), represents a predicate (a property) and represents an object (either an entity or a data value like date and number). An entity can belong to one or more classes, which is defined by the property rdf:type.

Such a KB is often called an RDF-based KB. It can be accessed by SPARQL queries. Two examples used in our method are () getting entities of a given class according to rdf:type, and () getting triples whose subject entity is given. SPARQL supports semantic reasoning for accessing implicit knowledge [Glimm and Ogbuji2013]; for example, inferring , given and . A KB can also be accessed via fuzzy matching, with a lexical index on entity labels (phrases defined by rdfs:label) and sometimes entity anchor text (short descriptions). This is often referred to as KB lookup. Successful systems include Spotlight for DBpedia [Mendes et al.2011] and OpenRefine for Wikidata [Ham2013].

2.3.2 Candidate Properties

Given a class defined by a KB, we denote entities that belong to it as . It means the triple is true for any entity in . Given a property defined by a KB, an entity is defined as a subject entity of , denoted as , if there exists at least one object such that the triple is entailed by the KB. We denote all the subject entities of the property as . A property is defined as a frequent property of class , denoted as , if , where is a threshold and denotes the cardinality of a set. “Frequent” means at least a specified proportion of the entities of a class are associated to that specific property.

A candidate property represents a potential relationship between two columns. To get candidate properties, we first extract the frequent properties of each candidate (training) class , denoted as , and then merge these frequent properties: . The size of is denoted as . The above calculation requires SPARQL queries of type and SPARQL queries of type .

2.3.3 Property Vector (P2Vec)

Property features of one micro table are represented by a P2Vec denoted as . Each slot of represents the degree of existence of one candidate property, and thus the dimension of is . The calculation of P2Vec is shown in Algorithm 1. Given a micro table, it first retrieves KB entities that match the main cell (Line 1). As lookup by lexical matching is ambiguous, entity_lookup is set to return more than one entity (at most ) to avoid missing the right entity. For each matched entity, it first retrieves its property annotations, namely the triples whose subject is this entity, using a SPARQL query of type (Line 1 to 1), and then matches each triple’s object with the first cell of each surrounding column (Line 1 to 1).

In matching, the function cell_object_match

first classifies the object

into types of entity, date, text and number, and then returns true or false with the following processing. An entity is transformed to a phrase with its English label defined by rdfs:label, while a date is transformed to an integer that represents the year. In comparing two texts, it returns true if their string-edit distance (e.g., Jaro Distance [Cohen et al.2003]) exceeds the threshold and false otherwise, while in comparing two numbers, it returns true if they are equal and false otherwise. Note that we do not return a matching degree score but true or false, so as to leave salient predictive information about inter-column relations with less noise.

Algorithm 1 needs once entity lookup, at most SPARQL queries of type Q2, and matchings with function cell_object_match.

1 Input: (i) A micro table , (ii) candidate properties with the size of , (iii) a maximum number of matched entities , (iv) a text matching threshold ,
2 Result: : a property vector of the micro table
3 begin
4        ; Init. of the property vector
5        ; Entity lookup by main cell
6        foreach entity  do
7               ; Get triples whose subject is
8               foreach triple with  do
9                      foreach surrounding column  do
10                             if  then
11                                    ;
12                                    ; Set the slot of the property
13                                   
14                            
15                     
16              
17       ; Normalization
18
return
Algorithm 1 P2VecExtract

2.4 Ensemble

P2Vec is integrated with the HNN by two ensemble approaches. Ensemble I first trains a basic multi-class classifier e.g., Multiple Layer Perception (MLP) and predicts the score:

(9)

where the average word vector of the main cell is concatenated with the P2Vec as the input. It then calculates the average of the above score and the score by the HNN (8):

(10)

Ensemble II trains a multiple-class classifier with the concatenation of the P2Vec and the FC layer output of the HNN (7), and predicts the score:

(11)

In decision making, the class with the highest score is adopted as the column type.

3 Evaluation

In the evaluation111Codes: https://github.com/alan-turing-institute/SemAIDA conducted in this paper we rely on DBpedia and three web table sets: T2Dv2222http://webdatacommons.org/webtables/goldstandardV2.html from the general Web, Limaye [Limaye et al.2010] and Efthymiou [Efthymiou et al.2017] from the Wikipedia encyclopedia. We annotate (i) entity columns of T2Dv2 with concrete and disjoint classes defined by the DBpedia ontology, (ii) entity columns of Limaye with out of the above classes, and (iii) entity columns of Efthymiou with out of the above classes. T2Dv2 is randomly split into T2D-Tr () and T2D-Te (). All the results except for Table 3 are based on the following setting: T2D-Tr is used for training, while T2D-Te, Limaye and Efthymiou are used as three testing sets. We report accuracy, i.e., the ratio of correctly labeled columns.

The reported results are based on the following hyper parameter setting. Regarding the micro table, the number of rows is set to , the number of surrounding columns is set to , and zero-padding is used for tables that do not have enough columns or rows. In training, negative samples are constructed by labeling the entity column with each wrong class; a word2vec model [Mikolov et al.2013] trained by the latest dump of Wikipedia articles is adopted. HNN is trained by Adam [Kingma and Ba2014]

with the loss function of softmax cross entropy. The hidden size and the attention layer size of RNN are set to

and , the column Conv filter set and the row Conv filter set are set to and , the feature number per filter ( and ) is set to . In computing P2Vec, the DBpedia lookup service333https://github.com/dbpedia/lookup and SPARQL endpoint444http://dbpedia.org/sparql are used, while the hyper parameters , and are set to , and respectively.

In evaluation, we adopt as baselines two typical multi-class classifiers – Logistic Regression (LR) and Multiple Layer Perception (MLP), variants of our HNN (including ColNet

[Chen et al.2019]), and two lexical matching based column type annotation methods – DBpedia lookup service plus majority voting by matched entities [Zwicklbauer et al.2013] (Lookup-vote) and T2K Match [Ritze et al.2015]. LR and MLP are also used as the classifier for ensemble. In the following, we first consider the effectiveness of HNN and P2Vec and then evaluate the overall result, with the transferability between table sets analyzed.

3.1 Hybrid Neural Network

In Table 1, we can see that the HNN variants with both Att-BiRNN and CNN achieve the highest accuracy on all three testing sets. In the following, we separately analyze the impact of Att-BiRNN and CNN.

Att-BiRNN. In comparison with word vector averaging, embedding the cell phrase by Att-BiRNN improves the model’s accuracy. In Table 1, Att-BiRNN outperforms word2vec-avg + FC-Softmax by , and on T2D-Te, Limaye and Efthymiou respectively. When a CNN is stacked, embedding by Att-BiRNN is still beneficial. For instance, Att-BiRNN + outperforms word2vec-avg + by , and on the three testing sets.

Methods T2D-Te Limaye Efthymiou
word2vec-avg + FC-Softmax
word2vec-avg +
word2vec-avg +
word2vec-avg +
Att-BiRNN
Att-BiRNN +
Att-BiRNN +
Att-BiRNN +
Table 1: Accuracy of HNN variants. word2vec-avg represents averaging the word2vec of words of each cell phrase. FC-Softmax denotes a classifier by a FC layer and a Softmax layer. The superscripts c and r of CNN denote Conv filters over the column and row.

Column Features. Conv filters over the target column learn column features. According to Table 1, they are effective in improving the accuracy. For example, word2vec-avg + outperforms word2vec-avg + FC-Softmax by , and on T2D-Te, Limaye and Efthymiou respectively. When the embedding by Att-BiRNN is used, they are still beneficial. The corresponding improvement of Att-BiRNN + over Att-BiRNN + FC-Softmax is , and . The limited improvement on T2D-Te is due to the high base accuracy (T2D-Te comes from the same table set as the training data).

Row Features. Conv filters over the row of the main cell learn row features. Unlike column features, the impact of row features varies from data to data, as seen in Table 1. For example, with Att-BiRNN, adding improves the accuracy by on Limaye but reduces the accuracy by and on T2D-Te and Efthymiou respectively. One potential reason is that the noise from surrounding columns overwhelms the learned discriminative patterns due to factors like varying relative position between a target column and a surrounding column (e.g., a column of book names vs a column of writer names) from table to table. This explanation is supported by the results in Figure 2 using the basic classifiers LR and MLP. As with adding row feature via CNN, concatenating the average word2vec of cells of surrounding columns increases the accuracy on Limaye but reduces the accuracy on T2D-Te and Efthymiou.

Although row features do not always improve the accuracy, they are still beneficial in comparison with directly concatenating the average word2vec of cells of surrounding columns, leading to higher improvement on Limaye and lower decreasement on T2D-Te and Efthymiou, as seen in Figure 2.

Figure 2: Accuracy improvement using surrounding columns. Cells of surrounding column are appended to the main cell through vector concatenation (word2vec-avg + LR and word2vec-avg + MLP) and row feature learning ( and Att-BiRNN + ).

3.2 Property Vector

The results in Figure 3 illustrate the effectiveness of P2Vec in column type prediction. On the one hand, appending P2Vec to the main cell (i.e., Main Cell + P2Vec) significantly improves accuracy; e.g., the improvement of MLP is , and on T2D-Te, Limaye and Efthymiou respectively. This is much higher than directly concatenating average word vectors of cells of surrounding columns in the row (i.e., Main Row). The latter actually negatively impacts performance on T2D-Te and Efthymiou, which is consistent with the impact of row features learned by Conv filters in HNN. On the other hand, we find that feeding LR and MLP with P2Vec concatenation even outperforms the HNN that learns row feature. For example, Main Cell + P2Vec with LR in Figure 3 outperforms Att-BiRNN + in Table 1 by , and respectively on T2D-Te, Limaye and Efthymiou.

Figure 3: Accuracy with and without P2Vec concatenation. Average word2vec is used for cell embedding.

In Figure 4 we analyze the distribution of non-zero elements of P2Vec and its impact on performance improvement by P2Vec. P2Vec shows significant performance improvement on “Book”, “Newspaper” and “Monarch”, and at the same time has significant Hits# and zero Noise# (except for “Monarch” of Efthymiou). This indicates the positive impact of the correctly matched properties. Meanwhile we find there are no or limited improvements on the other classes although most of them also have significant Hits#. This is due to (i) the high base accuracy without P2Vec (e.g., close to for “Bird” and “University” of Limaye and Efthymiou), and (ii) the negative impact of Noise# (e.g., “Writer” of Efthymiou).

Figure 4 also shows that Limaye has higher Hits# and lower Noise# than Efthymiou. This in some degree explains why P2Vec achieves more significant improvement on Limaye than on Efthymiou ( vs for the average accuracy gap of the classes in Figure 4; vs for the improvement by P2Vec in Figure 3). Meanwhile, the low absolute value of Hits# and Noise# means P2Vec is quite sparse – less than out of slots are none zero. Sparsity reduces the training time and helps avoid over fitting.

Figure 4: Average number of correctly and incorrectly matched properties per row, i.e., correct and incorrect none zero elements per P2Vec (Hits# and Noise#), and the accuracy improvement (gap) of LR by appending P2Vec to the main cell, on classes.

3.3 Ensemble

As seen in Table 2, both ensemble approaches are beneficial. Ensemble I achieves higher accuracy than P2Vec and HNN on T2D-Te which comes from the same table set as the training data. Ensemble II always achieves accuracy very close to the highest of P2Vec and HNN on all three testing sets, e.g., vs

on Efthymiou. Ensemble I outperforms Ensemble II on T2D-Te, while Ensemble II outperforms Ensemble I on Limaye and Efthymiou. Thus, we can apply Ensemble I in contexts where training and testing data come from the same source, and apply Ensemble II in contexts that need high robustness. Considering Ensemble I re-trains a classifier with FC layer output of the trained HNN and P2Vec, and is more likely to be over-fitted to the training data, it is unsurprising to see its performance drop on Limaye and Efthymiou as the training data comes from T2Dv2. This also indicates the difficulty of transferring learned table features and models between data sets.

Methods T2D-Te Limaye Efthymiou
P2Vec
HNN
Ensemble I (P2Vec + HNN)
Ensemble II (P2Vec + HNN)
Table 2: Accuracy of P2Vec, HNN, and the ensemble approaches. Both LR and MLP are used and the average is reported.

3.4 Overall Result and Discussion

As shown in Table 3, our method (HNN + P2Vec) dramatically outperforms Lookup-Vote and T2K Match that use lexical matching, and ColNet that uses deep learning, when the training and testing data comes from the same table set (Local-70%). Its accuracy is , and higher than Lookup-Vote, , and higher than ColNet, on T2D, Limaye and Efthymiou respectively. Although the assumption on training data would constrain applicability, the case that some columns have been annotated (e.g., by volunteers) while many more from the same source remain to be annotated is quite common. On the other hand, when trained on one table set (T2D-Tr) and transferred to another (Limaye and Efthymiou), the performance of HNN + P2Vec decreases but is still higher than ColNet. One cost sensitive solution for such a transfer setting is combining T2D-Tr with a small number of labeled columns from the testing set (Local-10%); its performance on Limaye is then and higher than Lookup-Vote and T2K Match respectively.

Methods (Training Data) T2D-Te Limaye Efthymiou
HNN + P2Vec (T2D-Tr)
HNN + P2vec (Local-70%)
HNN + P2vec (T2D-Tr + Local-10% ) -
Lookup-Vote
T2K Match 0
ColNet (T2D-Tr)
ColNet (Local-70%)
Table 3: Accuracy of the baselines and our method under different training data settings. Local- represents randomly extracting of a table set as training data, with the remainder as testing data.

Discussion. In the evaluation we first analyzed the impact of components of HNN. Cell embedding by Att-BiRNN and column features by Conv filters over the target column achieve significant accuracy gains as expected, while row features by Conv filters over the row of the main cell have a positive impact on only one out of three testing sets, which may be caused by varying table structures such as different column permutations. Second, we evaluated P2Vec which is extracted by a KB lookup and query answering algorithm and includes information about potential relations between the target column and surrounding columns. It achieves significant improvement, thus compensating for the above weak row features. Third, we analyzed two ensemble approaches that combine P2Vec and HNN. They lead to better and more robust performance. Finally we compared our method with some state-of-the-art baselines including those using deep learning (i.e., variants of HNN) and those using lexical matching (i.e., Lookup-Vote and T2K Match). Our method significantly outperforms lexical matching when the training data or a part of the training data comes from the same source as the testing data, but transferring the model trained on one table set to another totally different one for testing is still a big challenge.

4 Related Work

Most semantic table annotation works are based on lexical matching between table and KB [Venetis et al.2011, Pham et al.2016, Cafarella et al.2018]. State-of-the-art performance is achieved by jointly considering different matching tasks. These methods include variants of probabilistic graphical models [Limaye et al.2010, Mulwad et al.2013, Bhagavatula et al.2015], scoring models [Chu et al.2015], T2K Match [Ritze et al.2015], Table Miner [Zhang2017], etc. Performance also depends on the quality of the lexical index. For example, the lookup service powered by the index of DBpedia Spotlight [Mendes et al.2011] can achieve good performance in cell to entity matching and column type annotation (i.e., Lookup-Vote) [Chen et al.2019]. However, most of the above methods rely on table meta data for high performance, while lexical matching in principle fail to capture the contextual meaning of cell phrases.

Recently, with the development of deep learning, semantic embedding techniques like word2vec [Mikolov et al.2013] have been applied and methods that learn table features have been proposed. Both [Efthymiou et al.2017] and [Kunihiro et al.2019] utilize KB embedding. The former explores the contextual semantics of an entity in the KB for disambiguation in cell to entity matching, while the latter accelerates searching and deals with the missing linkage in column to class matching with Markov Random Field. [Luo et al.2018], [Nishida et al.2017] and [Chen et al.2019] all explore table feature learning with neural networks. The former two learn cell features and locality features as our HNN, but deal with totally different problems. [Luo et al.2018] matches a cell to an entity in a different language, while [Nishida et al.2017] classifies the structure of a table. In ColNet [chen2019colnetwepredictcolumntypeswitha] different problem setting with unfixed candidate classes and multiple binary classifiers. ColNet’s architecture is a special case of our HNN, namely word2vec + in Table 1. Briefly, learning the semantics of tabular data is promising, but still a big challenge [Thirumuruganathan et al.2018].

5 Conclusion and Outlook

In this study we predict the semantic type of entity columns, using a hybrid neural network (HNN) for cell embedding and table feature learning, and a property vector (P2Vec), extracted by KB lookup and query answering, for semantic features that represent potential inter-column relations. We evaluated our method with DBpedia and three web table sets; it is effective in most cases, and the overall performance exceeds the state-of-the-art in the supervised learning setting. We also considered generalisation across data sets, but this proved to be more challenging. In the future we will apply our approach in an AI assistant for data analytics, and further investigate (permutation invariant) table feature learning.

6 Acknowledgments

We want to thank Chris Williams from University of Edinburgh for his constructive comments. The work is supported by the AIDA project (UK Government’s Defence & Security Programme in support of the Alan Turing Institute), the SIRIUS Centre for Scalable Data Access (Research Council of Norway, project 237889), the Royal Society, EPSRC projects DBOnto, and .

References

  • [Bhagavatula et al.2015] Chandra Sekhar Bhagavatula, Thanapon Noraset, and Doug Downey. Tabel: entity linking in web tables. In ISWC, pages 425–441, 2015.
  • [Cafarella et al.2008] Michael J Cafarella, Alon Halevy, Daisy Zhe Wang, Eugene Wu, and Yang Zhang. Webtables: exploring the power of tables on the web. Proceedings of the VLDB Endowment, 1(1):538–549, 2008.
  • [Cafarella et al.2018] Michael Cafarella, Alon Halevy, Hongrae Lee, Jayant Madhavan, Cong Yu, Daisy Zhe Wang, and Eugene Wu. Ten years of webtables. Proc. VLDB Endow., 11(12):2140–2149, August 2018.
  • [Chen et al.2019] Jiaoyan Chen, Ernesto Jimenez-Ruiz, Ian Horrocks, and Charles Sutton. Colnet: Embedding the semantics of web tables for column type prediction. In AAAI, 2019.
  • [Chu et al.2015] Xu Chu, John Morcos, Ihab F Ilyas, Mourad Ouzzani, Paolo Papotti, Nan Tang, and Yin Ye. Katara: A data cleaning system powered by knowledge bases and crowdsourcing. In Proceedings of ACM SIGMOD, pages 1247–1261. ACM, 2015.
  • [Cohen et al.2003] William Cohen, Pradeep Ravikumar, and Stephen Fienberg. A comparison of string metrics for matching names and records. In Kdd workshop on data cleaning and object consolidation, volume 3, pages 73–78, 2003.
  • [Domingue et al.2011] John Domingue, Dieter Fensel, and James A Hendler. Handbook of semantic web technologies. Springer Science & Business Media, 2011.
  • [Efthymiou et al.2017] Vasilis Efthymiou, Oktie Hassanzadeh, Mariano Rodriguez-Muro, and Vassilis Christophides. Matching web tables with knowledge base entities: from entity lookups to entity embeddings. In ISWC, pages 260–277. Springer, 2017.
  • [Glimm and Ogbuji2013] Birte Glimm and Chimezie Ogbuji. Sparql 1.1 entailment regimes. W3C Recommendation, 2013.
  • [Ham2013] Kelli Ham. Openrefine (version 2.5). http://openrefine. org. free, open-source tool for cleaning and transforming data. Journal of the Medical Library Association: JMLA, 101(3):233, 2013.
  • [Kim2014] Yoon Kim. Convolutional neural networks for sentence classification. In EMNLP, pages 1746–1751, 2014.
  • [Kingma and Ba2014] Diederik P Kingma and Jimmy Ba. Adam: A method for stochastic optimization. arXiv preprint arXiv:1412.6980, 2014.
  • [Kunihiro et al.2019] Takeoka Kunihiro, Oyamada Masafumi, Nakadai Shinji, and Takeshi Okadome. Meimei: An efficient probabilistic approach for semantically annotating tables kunihiro. In AAAI, 2019.
  • [Limaye et al.2010] Girija Limaye, Sunita Sarawagi, and Soumen Chakrabarti. Annotating and searching web tables using entities, types and relationships. Proceedings of the VLDB Endowment, 3(1-2):1338–1347, 2010.
  • [Luo et al.2018] Xusheng Luo, Kangqi Luo, Xianyang Chen, and Kenny Q Zhu. Cross-lingual entity linking for web tables. In AAAI, pages 362–369, 2018.
  • [Mendes et al.2011] Pablo N Mendes, Max Jakob, Andrés García-Silva, and Christian Bizer. Dbpedia spotlight: shedding light on the web of documents. In Proceedings of the 7th international conference on semantic systems, pages 1–8. ACM, 2011.
  • [Mikolov et al.2013] Tomas Mikolov, Ilya Sutskever, Kai Chen, Greg S Corrado, and Jeff Dean. Distributed representations of words and phrases and their compositionality. In Advances in neural information processing systems, pages 3111–3119, 2013.
  • [Mulwad et al.2013] Varish Mulwad, Tim Finin, and Anupam Joshi. Semantic message passing for generating linked data from tables. In ISWC, pages 363–378, 2013.
  • [Nishida et al.2017] Kyosuke Nishida, Kugatsu Sadamitsu, Ryuichiro Higashinaka, and Yoshihiro Matsuo. Understanding the semantic structures of tables with a hybrid deep neural network architecture. In AAAI, pages 168–174, 2017.
  • [Pham et al.2016] Minh Pham, Suresh Alse, Craig A Knoblock, and Pedro Szekely. Semantic labeling: a domain-independent approach. In ISWC, pages 446–462, 2016.
  • [Ritze et al.2015] Dominique Ritze, Oliver Lehmberg, and Christian Bizer. Matching html tables to dbpedia. In Proceedings of the 5th International Conference on Web Intelligence, Mining and Semantics, pages 1–6. ACM, 2015.
  • [Ritze et al.2016] Dominique Ritze, Oliver Lehmberg, Yaser Oulabi, and Christian Bizer. Profiling the potential of web tables for augmenting cross-domain knowledge bases. In WWW, pages 251–261, 2016.
  • [Thirumuruganathan et al.2018] Saravanan Thirumuruganathan, Nan Tang, and Mourad Ouzzani. Data curation with deep learning [vision]: Towards self driving data curation. arXiv preprint arXiv:1803.01384, 2018.
  • [Venetis et al.2011] Petros Venetis, Alon Halevy, Jayant Madhavan, Marius Paşca, Warren Shen, Fei Wu, Gengxin Miao, and Chung Wu. Recovering semantics of tables on the web. Proceedings of the VLDB Endowment, 4(9):528–538, 2011.
  • [Yang et al.2016] Zichao Yang, Diyi Yang, Chris Dyer, Xiaodong He, Alex Smola, and Eduard Hovy. Hierarchical attention networks for document classification. In NAACL-HTL, pages 1480–1489, 2016.
  • [Zhang2017] Ziqi Zhang. Effective and efficient semantic table interpretation using tableminer+. Semantic Web, 8(6):921–957, 2017.
  • [Zwicklbauer et al.2013] Stefan Zwicklbauer, Christoph Einsiedler, Michael Granitzer, and Christin Seifert. Towards disambiguating web tables. In ISWC, pages 205–208, 2013.