<!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>Relational Search and its Application to Investigative Intelligence Scenarios⋆</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Discussion Paper</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stéphane Campinas</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Matteo Catena</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Renaud Delbru</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Siren (https:// siren.io)</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Galway</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ireland</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>Data-driven investigation intelligence systems are critical to the Intelligence and Defense domains to detect and prevent existing, evolving, and emerging criminal activities such as cyber-threats, human traficking, money laundering, frauds, and crime rings. Several technical and usability challenges must be tackled to implement an efective investigative intelligence system. For instance, the ever-increasing volume and complexity of information form a fertile ground for malicious actors to blend in and operate, and investigations often involve connecting the dots on both large quantities of structured (well-defined records), semi-structured (logs), and unstructured data (textual and other media). In a Law Enforcement scenario, this could mean connecting tables of vehicles, cases, and trafic camera license plate readings, while it is common to use concepts such as IPs, MD5 hash values, or user IDs to tie together security logs in a Cybersecurity scenario. Therefore, investigative systems must provide intuitive and scalable ways to search, explore, and analyze large relational datasets. With information that is often interconnected in essence, such systems must also enable a mixed workload of search, data and graph analytics to support users in examining records and their relationships from diferent perspectives. Finally, analysts often interact with the system by following an explorative and iterative process that represents their train of thoughts. Consequently, investigative systems must have fast response times to avoid impeding the mental process of the analysts. With roots in Information Retrieval research applied to the faceted exploration of Linked Data [1, 2], Siren provides an investigative intelligence platform called Investigate [3, 4] which is based on Elasticsearch and on the Siren's Elasticsearch plugin called Federate [3, 5]. The platform gives analysts several data interaction paradigms, such as search, analytic dashboard, set-to-set navigation, and graph visualization, and combines them into a unified and coherent interaction model. For example, the set-to-set navigation helps analysts to express their information needs visually, by connecting together diferent areas of interest. Applying filters on a set has an impact on all (in)directly connected sets, which allows an analyst to view only the relevant information for a given need. For instance, in a Financial Investigation scenario, we could have data on companies that have received investments from investors but are also mentioned by articles and have headquarters in cities. Siren Investigate can move from a set of companies to the set of records connected to it - for example, the investments received by Irish companies</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>that are mentioned in articles regarding Artificial Intelligence. The graph visualization instead
helps an analyst to have an overview of the computed sets, to see if any pattern or clusters
emerge. In our example, graph visualization can help to picture the answers to questions like
“Which investors invested in which companies? Are they investing in pairs or groups? Are there
groups that appear to be investing in competing companies?”.</p>
      <p>
        Eficient relation search capabilities are essential for implementing both set-to-set and graph
visualization paradigms. Regrettably, document-oriented databases like Elasticsearch present
some limitations in joining data. For instance, joining must be planned in advance at document
indexing-time, and the documents to be joined must reside in the same index and on the
same shard for scalability reasons [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. This is adequate for hierarchical relationships but does
not easily support more complex relationship models (e.g., networks) without incurring data
duplication. The Federate plugin addresses these constraints by incorporating a query-time
distributed semi-join operation between diferent inverted indices, and an efective caching
mechanism for join results [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Consequently, Federate significantly enhances the flexibility
and performance of the platform, facilitating complex tasks that are crucial for investigative
intelligence such as extracting the shortest paths between entities in a graph.
      </p>
      <p>In this talk, we will explore how the Siren Federate plugin integrates relational search
capabilities into Elasticsearch and how it empowers the Siren Investigate platform to tackle
some of the challenges in Investigative Intelligence. Specifically, we will discuss:
• Enabling analysts to devise custom data models that describe relationships between
records,
• Supporting set-to-set navigation for interactive exploration and defining information
needs,
• Utilizing graph visualization to uncover patterns within the data.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>E.</given-names>
            <surname>Oren</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Delbru</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Decker</surname>
          </string-name>
          ,
          <article-title>Extending faceted navigation for rdf data</article-title>
          ,
          <source>in: Proceedings of the 5th International Conference on The Semantic Web, ISWC'06</source>
          , Springer-Verlag, Berlin, Heidelberg,
          <year>2006</year>
          , p.
          <fpage>559</fpage>
          -
          <lpage>572</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>R.</given-names>
            <surname>Delbru</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Campinas</surname>
          </string-name>
          , G. Tummarello,
          <article-title>Searching web data: An entity retrieval and high-performance indexing model</article-title>
          ,
          <source>Web Semant</source>
          .
          <volume>10</volume>
          (
          <year>2012</year>
          )
          <fpage>33</fpage>
          -
          <lpage>58</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Siren</given-names>
            <surname>Platform - Version 13 Product Overview</surname>
          </string-name>
          ,
          <year>2022</year>
          . URL: https://info.siren.io/content/ siren-13
          <string-name>
            <surname>-</surname>
          </string-name>
          product-overview-whitepaper,
          <source>last accessed: May</source>
          <volume>30</volume>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4] Introduction to Siren Platform,
          <year>2020</year>
          . URL: https://docs.siren.
          <article-title>io/siren-platform-user-</article-title>
          <source>guide/ 13</source>
          .2/index.html,
          <source>last accessed: May 3</source>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5] Introduction to Siren Federate,
          <year>2020</year>
          . URL: https://docs.siren.
          <article-title>io/siren-federate-user-guide/ 31/siren-federate/introduction</article-title>
          .html,
          <source>last accessed: May 3</source>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>Elasticsearch</given-names>
            <surname>Guide</surname>
          </string-name>
          : Joining queries,
          <year>2023</year>
          . URL: https://www.elastic.co/guide/en/ elasticsearch/reference/current/joining-queries.html,
          <source>last accessed: May 3</source>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <source>[7] Joining 15 Billion Records in Seconds: the New Siren Benchmark</source>
          ,
          <year>2022</year>
          . URL: https://info. siren.io/content/siren-benchmark-whitepaper,
          <source>last accessed: May</source>
          <volume>30</volume>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>