<!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>Open the Pod Bay Door: Using Ontology to Understand Instructions1</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Yixin SUN</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael GRU¨ NINGER</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Mechanical and Industrial Engineering, University of Toronto</institution>
          ,
          <addr-line>Ontario</addr-line>
          ,
          <country country="CA">Canada</country>
          <addr-line>M5S 3G8</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>There have been a great deal of developments and implementations for conversational robots like Amazon Alexa, and Google Home. Yet, little research has been done for robots to understand a more rigorously structured, instructionwise natural language. In this paper, we present an ontology approach to convert instructions from natural language to logical formulas, Process Specification Language (PSL) in this case. Verbs, therefore, are treated as indication of actions or processes and are decomposed semantically to understand meanings. As a method of evaluating this approach, verbs, originally in PSL, are worked towards natural language. In this paper, we present how to take natural language instructions and map them to appropriate cutting classes; and moreover, we present the capability of this ontology-centered approach to go in a reverse direction (from PSL to natural language).</p>
      </abstract>
      <kwd-group>
        <kwd />
        <kwd>process ontology</kwd>
        <kwd>semantic parsing</kwd>
        <kwd>instructions</kwd>
        <kwd>cutting process</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>In the movie, 2001: A Space Odyssey, the ship’s computer Hal would not follow Dave’s
spoken instructions, and did not open the pod door. When someone utters ”open the pod
bay door”, indeed, only the end result is specified, lacking all of the detailed steps in
between. This door example best mimics human-to-human instruction, as opposed to the
way that programmers will hard-code an autonomous robot, stressing even the robot’s
exact angle with the door knob. This paper focuses on a higher level of abstraction and
thus studies how a robot can understand instructions uttered in natural language. The
form of matters we have based our research on is verbal instructions, which is inspired
by the notion of Physical Turing Test.</p>
      <p>The Physical Turing Test extends the Turing Test by specifying questions that
require the integration of perception, reasoning, and action. In particular, Ortiz et al [1]
propose two tracks for the Physical Turing Test. The Construction Track focuses on
building predefined structures (such as a tent or modular furniture) given a combination of
verbal instructions and images. The research presented in this paper is motivated by the
following long-term vision related to the Construction Track:</p>
      <sec id="sec-1-1">
        <title>Given a set of verbal instructions, together with a sequence of annotated images, answer questions about the activities that can possibly occur during performance of the instructions and the various objects that participate in these activity occurrences.</title>
        <p>In particular, we write out instructions not in a step-by-step manner, but in the most
usual way for a worker or a practitioner to follow. By mapping natural language to the
Process Specification Language (PSL) Ontology [2], we approach the problem by
matching action verbs in a sentence to a particular process and then mapping this process to
a first-order logic formula. Understanding verbs becomes our primary goal moving
forward. Furthermore, in order to validate whether the process generated from natural
language is correct or not, we can invert this approach and remap the logical formula - that
is the PSL process description - to natural language. This is a proof-of-concept paper
that proposes how semantic parsing can work from an ontology-focused perspective and
verifies its feasibility.</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>2. Literature Review</title>
      <p>The Alexa Meaning Representation Language (AMRL) [3] introduced a graphical
hierarchy of the main Amazon Alexa ontology with nodes and arcs. Classes (each represented
by a node) are connected with a property (an arc) in between, while children classes are
connected to parent classes. In this way, Amazon Alexa can understand a more complex
and cross-domain conversation. In this study, Amazon Alexa had better performance in
solving ambiguities when mapped to AMRL, rather than spoken language
understanding. This study mainly sought solutions for flexibility and ambiguity in which its
approach could be useful to our study. Nonetheless, our focus differs from Amazon Alexa
insofar as we are not interested in daily conversational languages; instead, we are
seeking to understand a more formally written language which can be best represented by the
category of instructions.</p>
      <p>According to Levin’s definition of English Verb Classes [4], verbs can be divided
into four categories: hit verb, touch verb, cut verb, and break verb. These classes differ
by whether a change of state occurs, whether a contact with another object is made, and
whether it in nature is a causative/inchoative motion, respectively. Under each category
lies different subclasses, categorized by whether or not the subclass passes the designated
alteration tests. Based on the nature of the tests, verbs belong to the same classes and
subclasses do not necessarily imply they are synonyms. Classifying verbs in this way can
only provide guidance to syntactic uses. VerbNet [5] further extends Levin’s idea to a
coding library that can be imported into Java/Python/C++. However, this package is not
comprehensive enough to be incorporated into our study as each subclass has a limited
number of sample verbs.</p>
      <p>Nonetheless, Levin has pointed out a possible approach for instruction mapping:
verb synonyms under the same subclasses can be used in the same sentence and convey
the same meaning. In this way, The Cutting Process Ontology [6] proposed nine different
ways of cutting a two-dimensional piece of sheet metal. The paper introduced three new
topological components: points, edges and surfaces. An edge is a subset of at least two
points, while a surface is a subset of at least two edges. Furthermore, other definitions
can be built on top of the existing components. For instance, a hole is a hollow surface
within a solid one. The PSL Ontology was used to axiomatize the cutting processes in
terms of whether any edges, holes and/or surfaces were created/destroyed (see Figure 1).
e4
e4
e1</p>
      <p>e7</p>
      <p>Through mapping natural language expressions to the Cutting Process Ontology,
synonyms of “cut” such as “chip”, “split”, “snip” all belong to the same subclass,
indicating that these synonyms can be represented by one or more of the cutting classes
identified in this paper. This indicates that synonyms can share some of the existing ontology
axioms. When it comes to translating instructions into PSL, this finding can be useful as
fewer new terms need to be created.</p>
      <p>Furthermore, physical cutting activities, in nature, are not limited to two-dimensional
shapes. Some of the instructions may require cutting action to be done on
threedimensional shapes when it comes to tree trunks or food recipes. There also lie some
intangible objects like movies, words and genes that when the cutting action were to be
performed on them, they would not change shape; instead they would change
sequencewise. To better describe all cutting processes and instructions, extending the cutting
ontology to include three-dimensional shapes can be considered for future work.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Approach</title>
      <p>We focus on developing an ontology-specific semantic parser, in which treats the action
verb as an utterance of processes and convert that into a first-order logic process
description. For evaluation and verification purposes, our approach can be proved by going
backwards in this pipeline. We can test the natural language instructions deduced from
the axioms against what people understand from natural language. Whether the two
utterances yield the same meaning can be treated as an evaluation criteria. The verb, “cut”
is taken as an example to demonstrate this process flow. See Figure 2 for details.</p>
      <sec id="sec-3-1">
        <title>3.1. Semantic Analysis in the context of PSL</title>
        <p>A PSL description is a logical formula that can specify an occurrence of activity in terms
of time-points while capturing changes in properties throughout the activity. We consider
the verb in a natural language sentence to be the representation of the activity that causes
objects to change state. In other words, only when something is done will the subjects
be affected. Therefore, the first thing to do is to locate where a verb is and of which two
words it falls in between; this can determine the primitive activity and the agent and/or
operator. A syntactic parsing tool, SpaCy [7], was applied to identify part-of-speech tags.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Cutting Ontology</title>
        <p>After natural language processing by SpaCy, we examine verbs specifically to interpret
their intended semantics. Motivated by the Cutting Process Ontology, topological
instructions were created based on existing PSL ontology. Since cutting is the verb in all
of the written instructions, by translating them into PSL, we hoped to find some
patterns that could apply universally in terms of converting instructions into logical
formulas. Therefore, the primary findings that will be presented in this paper centers around
the physical action verb, ”cut”. Figure 1 illustrates the nine different classes of cutting
activities and the corresponding changes to the shape of the object.</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Cutting Instructions</title>
        <p>In natural language, cutting is an action that does not require much description. It all
comes in naturally when a human were to cut something. This is evident in the data
collected from WikiHow.com 2 in which physical cutting activities do not stand alone
as an individual instruction of multiple steps to follow. Instead, the action of cutting is
mentioned in 193 different activities ranging from “cutting onions”, “cutting bread” to
paper cutting. Yet, ambiguity exists when the instructions given were “Cut a piece of
sheet metal”. Questions like “in what shape should the end result be” arise. Therefore,
to better examine the backward loop of converting natural language into PSL, we created
2Instruction data was scraped off from the website WikiHow.com as it was considered to be a go-to place for
real-life problems, ranging from math questions to furniture assembly and maintenance. In total, 922 rows of
data were scraped from the featured article page on May 6, 2020.
instructions in respect to the nine classes of cutting from a topological perspective. That
is, only relationships between edges, surfaces and holes were explained. Table 1 shows
the finalized written instructions with respect to the nine classes of the Cutting Process
Ontology [6].</p>
        <p>Continue from h),destroy the existing hole. Make a cut (Cut E) starting from any corner
(Corner A) of the outer rectangle, ending at a corner (Corner B) of the inner shape. This
cut should not cut through any part of the rectangle that does not have any material.</p>
        <p>Make a second cut (Cut F) starting from any point on the outer edge in which Corner
A intersects, ending at any point on the inner edge in which Corner B intersects. This
cut should not cut through any part of the rectangle that does not have any material.</p>
        <p>Two additional edges should be created. No extra surfaces should be created.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Shape Cutting Ontology</title>
      <p>Since PSL specifies a change of state, locations or directions, the starting position
mentioned in the written instruction were neglected. Only starting state and ending state
were taken into account. Following the open-the-door example mentioned in section 1,
human instructions are usually given in a higher level of abstraction. Correspondingly,
the classes of the Cutting Process Ontology were applied to instructions shown in
Table 1, and results can be found in Table 2.</p>
      <sec id="sec-4-1">
        <title>4.1. Discussion</title>
        <p>Axiomatization
preserve sur f ace(a) ^ preserve hole(a) ^ change one meet(a) ^ create three edge(a)
preserve sur f ace(a) ^ preserve hole(a) ^ change one meet(a) ^ create two edge(a)
create sur f ace(a) ^ preserve hole(a) ^ change one meet(a) ^ create f our edge(a)
create sur f ace(a) ^ preserve hole(a) ^ change one meet(a) ^ create three edge(a)
create sur f ace(a) ^ preserve hole(a) ^ change one meet(a) ^ create two edge(a)
preserve sur f ace(a) ^ destroy hole(a) ^ preserve meet(a) ^ create two edge(a)
preserve sur f ace(a) ^ destroy hole(a) ^ change one meet(a) ^ create f our edge(a)
preserve sur f ace(a) ^ destroy hole(a) ^ change two meet(a) ^ create f our edge(a)
preserve sur f ace(a) ^ destroy hole(a) ^ change one meet(a) ^ create two edge(a)
The instructions that we were able to recreate from the given illustrations have only
included the starting and ending state of the shape. As a result, only topological
relationships were involved, describing whether an edge, a surface, and/or a hole were to be
preserved or destroyed throughout the process. Yet, geometric relationships could also
be incorporated, making up a more detailed and thus more robotic-oriented instruction.
For instance, a geometric way of describing illustration (a) would be: On one width of
the rectangle, from any point excluding the corners, make a cut towards the centre of the
rectangle. The cut should not be parallel to the height of the rectangle. Stop before the
cut reaches the opposing width. From the end point of the cut, make another cut that ends
on any point of the original width excluding corners. This would be a detailed version
of how to make a cut, instead of only stressing the starting and ending conditions.
Geometric concepts are largely introduced here: “towards the centre”, “parallel to height”,
and etc. If this were to be the simplest version of cutting instructions, then the cutting
ontology would need an upgrade to include geometric definitions.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion</title>
      <p>This paper presents our initial efforts towards mapping natural language language
instructions to process descriptions using the PSL Ontology. In particular, cutting
processes are used as a demonstration of our approach. Meanwhile, as we explore mapping
procedures, we have found that going in the other direction - from PSL process
descriptions to natural language - can help us understand how instructions should be written
and interpreted. For example, in a day-to-day work routine, human beings communicate
instructions in a sense that specify end results, yet inevitably neglecting how to make a
cut. “How is cutting a sheet metal different from cutting a tree trunk?” is one possible
question that can arise in a physical Turing Test.</p>
      <p>Instructions, as a form of written natural language, tend to be more straight-forward
and less metaphorical. As for future studies, conversational natural language can be
studied that incorporate more rhetorical devices. For cutting instructions specifically, its
ontology could be extended in such a way that three-dimensional and intangible objects
will be included to accommodate a wider range of cutting instructions.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Ortiz</surname>
            , Jr,
            <given-names>C. L.</given-names>
          </string-name>
          (
          <year>2016</year>
          ).
          <article-title>Why We Need a Physically Embodied Turing Test and What It Might Look Like</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <source>AI Magazine</source>
          ,
          <volume>37</volume>
          (
          <issue>1</issue>
          ),
          <fpage>55</fpage>
          -
          <lpage>62</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>Gruninger</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2003</year>
          )
          <article-title>Ontology of the Process Specification Language</article-title>
          , pp.
          <fpage>599</fpage>
          -
          <lpage>618</lpage>
          , Handbook of Ontologies and Information
          <string-name>
            <surname>Systems</surname>
            , S. Staab (ed.). Springer-Verlag Kollar,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berry</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stuart</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Owczarzak</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chung</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mathias</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kayser</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Snow</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Matsoukas</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          (
          <year>2018</year>
          )
          <article-title>The Alexa Meaning Representation Language</article-title>
          .
          <source>Proceedings of the 2018 Conference of the North American Chapter of the Association for Computational Linguistics: Human Language Technologies</source>
          , Volume
          <volume>3</volume>
          (
          <string-name>
            <given-names>Industry</given-names>
            <surname>Papers) Levin</surname>
          </string-name>
          ,
          <string-name>
            <surname>B.</surname>
          </string-name>
          (
          <year>1993</year>
          )
          <article-title>English Verb Classes and Alternations: A Preliminary Investigation</article-title>
          . University of Chicago Press.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <surname>Brown</surname>
            <given-names>SW</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bonn</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gung</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zaenen</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pustejovsky</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Palmer</surname>
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2019</year>
          )
          <article-title>VerbNet Representations: Subevent Semantics for Transfer Verbs</article-title>
          .
          <source>Proceedings of the First International Workshop on Designing Meaning Representations.</source>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Gruninger</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Delaval</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2009</year>
          )
          <article-title>A First-Order Cutting Process Ontology for Sheet Metal Parts</article-title>
          , Fifth Conference on Formal Ontology Meets Industry, Vicenza, Italy.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>Choi</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tetreault</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stent</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          (
          <year>2015</year>
          )
          <article-title>It Depends: Dependency Parser Comparison Using a Web-based Exraction Tool</article-title>
          .
          <article-title>Proceedings of the 53rd Annual Meeting of the Association for Computational Linguistics and the 7th</article-title>
          <source>International Joint Conference on Natural Language Processing</source>
          , pages
          <fpage>387</fpage>
          -
          <lpage>396</lpage>
          ,Beijing, China,
          <source>July 26-31</source>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>