<!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>Developing a semantic event search engine for biomedical events</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Julio C. Rangel</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Norio Kobayashi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>RIKEN Information R&amp;D and Strategy Headquarters 2-1 Hirosawa</institution>
          ,
          <addr-line>Wako, Saitama, 351-0198</addr-line>
          <country country="JP">Japan</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We introduce Biomedical Event Finder (BEF), a semantic search engine that finds biomedical events (BE) from PubMed documents. BEF can be accessed via a web interface or a RESTful API. The simple retrieval of biomedical events from journal articles using keyword-based tools suffers from the issue of keyword mismatch; therefore, a key feature of our search engine is that it achieves semantic textual similarity via event embeddings to produce the most comparable results. We describe the primary components of our tool and our preliminary efforts</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;semantic search</kwd>
        <kwd>search engine</kwd>
        <kwd>biomedical event</kwd>
        <kwd>PubMed</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>The scientific literature has a massive quantity of relational knowledge, which includes
connections between biological entities such as proteins, medications, and symptoms. Researchers
are increasingly interested in extracting meaningful, organized, short, and clear information
about biomedical events to deal with the ever-increasing volume of publications. Biomedical
processes are modeled using biomedical event structures. Generally, they consist of signal
words, known as the event’s trigger, and biological things, known as the event’s arguments.
The trigger determines the event type, which specifies the semantics (or roles) of its parameters.
Typically, event triggers are nouns or verbs, such as oxidation, transcription, or reproduction,
whereas biological substances are usually proper nouns, such as DNA, ATP, or lactase. The role
theme defines the primary subject of attention in an event, whereas the role cause is frequently
the event’s facilitator or driver. Figure 1 depicts a typical event structure in the biomedical field.</p>
      <p>
        Even though the number of tools to extract biomedical events is growing each year [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ],
      </p>
      <sec id="sec-1-1">
        <title>Semantic Search</title>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Future work References</title>
      <p>existing search engines are not taking advantage of the data produced by such tools. In this
work, we first use DeepEventMine to create a dataset of events extracted from the PUDMED
baseline, which is then leveraged to develop a Faiss index to allow semantic search. To the best
of our knowledge, we are the first to attempt to construct a semantic searcher for biomedical
events on the whole PUBMED database.</p>
      <sec id="sec-2-1">
        <title>Extracting biomedical events</title>
        <p>First, we extracted cancer genetics (CG) and infectious disease (ID) events from 34 million
PubMed abstracts and titles using DeepEventMine (DEM). Because it generates over 1 TB of
BRAT standoff files, it is impractical to use the DEM tool directly on all PubMed records.The
standoff format is then omitted, and events are converted into a NetworkX graph and saved as
smaller JSON files. In addition, we increased GPU data processing to increase DEM’s speed.</p>
      </sec>
      <sec id="sec-2-2">
        <title>Index creation</title>
        <p>
          We generated a sentence-BERT embedding for each event graph by concatenating the names of
each node. In addition, index storage is reduced by decreasing the embedding dimension with
BERT-whitening [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. The resulting embeddings are converted into a Faiss flat index. To allow
search by year and event type (CG or ID), we created one index file for each year and event
type.
        </p>
        <p>BEF relies on a semantic search BERT layer to compare the event query to the year and event
type indexes. A query is embedded using Sentence-BERT and compared and rated against the
event-type and year indexes.</p>
        <p>Ongoing development is being done to enhance the performance of the engine as well as add
and expand functionalities. We will add GENIA, epigenetics (EPI), pathway curation (PC), and
MLEE to the list of biomedical events. To enhance the precision of the search, we intend to
develop and evaluate a variety of event embedding methods. In addition, we intend to generate
user-friendly visualizations for the events and normalize them according to ontologies.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Q.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Sheng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Cui</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Hei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Peng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Guo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Beheshti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. S.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <article-title>A compact survey on event extraction: Approaches and applications 14 (</article-title>
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>21</lpage>
          . URL: http://arxiv.org/abs/2107.02126.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J.</given-names>
            <surname>Su</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Cao</surname>
          </string-name>
          , W. Liu,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Ou</surname>
          </string-name>
          ,
          <article-title>Whitening sentence representations for better semantics and faster retrieval (</article-title>
          <year>2021</year>
          ). URL: http://arxiv.org/abs/2103.15316.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>