<!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>TableCNN: Deep Learning Framework for Learning Tabular Data ?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>University at Bu alo</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bu alo</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>IBM Research</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yorktown Heights</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>USA pranavgi@buffalo.edu</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>khabiri</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>bhavna</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>yingjieg@us.ibm.com</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>Databases and tabular data are among the most common and rapidly growing resources. But many of these are poorly annotated (lack su cient metadata), and are lled with domain speci c jargon and alpha-numeric codes. Because of the domain speci c jargon, no pretrained language model could be applied readily to encode the cell content. We propose a deep learning based framework, TableCNN, that encodes the semantics of the surrounding cells to predict the meaning of the columns. We propose application of Byte Pair Encoding (BPE)[5] to create tokens for each cell and treat each cell as a phrase of existing tokens. Once tokenized, we process it with a CNN network to develop a classi er.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
    </sec>
    <sec id="sec-2">
      <title>Methodology and Results</title>
      <p>
        Cell entries are tokenized using Byte-Pair Encoding with a stopping condition
de ned by the token frequency threshold. Cell embedding is generated using
Word2Vec[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]; each row across the tokenized table is treated as a sentence for
Word2Vec model learning. We extract micro tables from the table, with a target
column and surrounding columns having set number of rows; which are model
parameters. Micro tables are then processed through TableCNN to classify which
class it belongs to. Class is de ned as the header of a column in the table used
for training.
      </p>
      <p>Network: TableCNN Fig 1 is an abstract view of the TableCNN network
architecture. We extract column and row features in separate networks and
combine them to regress nal output. Row and column features are computed by a
convolution operation over the rst row and the target column of micro table
respectively. Outputs from row and column features are concatenated and fed
to a fully connected layer with a SoftMax layer to make nal prediction.</p>
      <p>For our experiment, we use a manufacturing database table that contains
112 columns and 115 thousand rows. Fig 2 shows that we obtain correct column
predictions, except for column 49. Upon further inspection, we found that most
of the cells in column 49 were empty, and thus the loss of classi cation accuracy.
This shows that network is able to learn features from the surrounding columns
along with the target column entries.</p>
    </sec>
    <sec id="sec-3">
      <title>Conclusions References</title>
      <p>In this poster, we present a supervised learning framework that can classify
columns of a table with arbitrary alpha-numeric data. The arbitrary
alphanumeric nature of data prevents us from using pre-trained language models.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Chen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jimenez-Ruiz</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sutton</surname>
            ,
            <given-names>C.A.</given-names>
          </string-name>
          :
          <article-title>Learning semantic annotations for tabular data</article-title>
          . CoRR abs/
          <year>1906</year>
          .00781 (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Efthymiou</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hassanzadeh</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodriguez-Muro</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Christophides</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Matching web tables with knowledge base entities: From entity lookups to entity embeddings</article-title>
          . In: International Semantic Web Conference (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Limaye</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sarawagi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chakrabarti</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Annotating and searching web tables using entities, types and relationships</article-title>
          .
          <source>PVLDB 3</source>
          ,
          <issue>1338</issue>
          {
          <volume>1347</volume>
          (09
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Mikolov</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chen</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Corrado</surname>
            ,
            <given-names>G.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dean</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>E cient estimation of word representations in vector space</article-title>
          .
          <source>CoRR abs/1301</source>
          .3781 (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Sennrich</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Haddow</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Birch</surname>
            ,
            <given-names>A.:</given-names>
          </string-name>
          <article-title>Neural machine translation of rare words with subword units</article-title>
          .
          <source>ArXiv abs/1508</source>
          .07909 (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>