<!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>Anu Question Answering System</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Balaji Ganesan</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Avirup Saha</string-name>
          <email>avirupsaha@iitkgp.ac.in</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jaydeep Sen</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Matheen Ahmed Pasha</string-name>
          <email>matpasha@in.ibm.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sumit Bhatia</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Arvind Agarwal</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>IBM Data and AI</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>IBM Research</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>IIT Kharagpur</institution>
          ,
          <country country="IN">India</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>AnuQA is a question answering system built on top of a search index and an enterprise knowledge graph. In this work, we describe ve semantic technologies that have helped us address real world challenges in deploying this system. These challenges include bias in knowledge base population, entity re-resolution on streaming data, ontology alignment across data sources, explaining relationships, and providing a single uni ed query interface for business analytics. [2] introduced the Anu Cognitive Compliance platform. It has enabled research in a number of elds including Search Index Optimization, Answer Sentence Selection, Document Similarity, Hypernym Discovery, Fine Grained Entity Classi cation, Ontology Creation and Link Prediction. We now present ve semantic technologies that we have implemented to enable real world deployments of AnuQA system.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Uni ed Hierarchical Label Set model for Ontology Alignment
AnuQA requires fusing information from di erent data sources to enable natural
language querying. This is typically handled by manual processes which become
cumbersome as the number of sources increases. We use the Uni ed Hierarchical
Label Set (UHLS) model [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], based on collective learning of entity types, to
integrate labels from di erent data sources and standard ontologies.
      </p>
    </sec>
    <sec id="sec-2">
      <title>Explainable Link Prediction</title>
      <p>
        While a number of interpretability solutions have been proposed for link
prediction by graph neural networks, human understandable explanations are
desirable in real world applications. Based on [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], we extract supporting text from
unstructured documents, logs, lineage data and relational tables. We also look
at existing paths to explain new links predicted between nodes in our knowledge
graph.
      </p>
    </sec>
    <sec id="sec-3">
      <title>Reasoning for Natural Language Interpretation</title>
      <p>
        Natural Language Query [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] interfaces allow end-users to ask questions without
knowing any specialized query language or data storage and schema details. We
use logical reasoning over domain semantics and knowledge to support a wide
variety of domain-speci c queries in natural language. Domain reasoning helps
us to make better interpretation of implicit intents in natural language queries,
especially analytic queries typically posed to information access systems.
Deployments
Di erent parts of this question answering system have been deployed in various
customer engagements and product o erings of IBM, especially in the nancial
services domain. http://covid19-india-qa.mybluemix.net is a sample instance of
the AnuQA system for answering questions on COVID19.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Abhishek</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Azad</surname>
            ,
            <given-names>A.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ganesan</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Anand</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Awekar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Collective learning from diverse datasets for entity typing in the wild</article-title>
          .
          <source>In: Proceedings of the 2nd International Workshop on EntitY REtrieval</source>
          . pp.
          <volume>16</volume>
          {
          <fpage>23</fpage>
          .
          <string-name>
            <surname>CEUR-WS</surname>
          </string-name>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Agarwal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ganesan</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gupta</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jain</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karanam</surname>
            ,
            <given-names>H.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kumar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Madaan</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Munigala</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tamilselvam</surname>
            ,
            <given-names>S.G.</given-names>
          </string-name>
          :
          <article-title>Cognitive compliance for nancial regulations</article-title>
          .
          <source>IT Professional</source>
          <volume>19</volume>
          (
          <issue>4</issue>
          ),
          <volume>28</volume>
          {
          <fpage>35</fpage>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bhatia</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dwivedi</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kaur</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>That's interesting, tell me more! nding descriptive support passages for knowledge graph relationships</article-title>
          .
          <source>In: International Semantic Web Conference</source>
          . pp.
          <volume>250</volume>
          {
          <fpage>267</fpage>
          . Springer (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Sen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ozcan</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Quamar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stager</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mittal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jammi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lei</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Saha</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sankaranarayanan</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Natural language querying of complex business intelligence queries</article-title>
          .
          <source>In: Proceedings of the 2019 International Conference on Management of Data</source>
          . pp.
          <year>1997</year>
          {
          <year>2000</year>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>