<?xml version="1.0" standalone="yes"?>
<Paper uid="W03-0905">
  <Title>The Genesis of a Script for Bankruptcy in Ontological Semantics</Title>
  <Section position="3" start_page="3" end_page="3" type="intro">
    <SectionTitle>
1 Introduction
</SectionTitle>
    <Paragraph position="0"> A spate of advanced new applications has called for a massive effort in script acquisition. Conceptualized as complex events, they have been provided for in the ontology since its inception (see Carlson and Nirenburg, 1990) and their format has always been reasonably well-defined as well as constantly adjusted to the consecutive releases (see Nirenburg and Raskin, 2003, Section 7.1.5; cf. Moreno Ortiz et al. 2002). Throughout the early and mid-1990s, however, lower-end NLP applications, such as knowledge- and meaning-based MT, did not necessitate a heavy use of scripts. The new generation of higher-end Q&amp;A and similar IE applications make it necessary to recognize individual events and their effects as part of scripts, both because humans do and because such recognition is necessary for establishing (co)reference relations. Thus, in the following text, only the availability of the BANKRUPTCY script can relate (i) and (ii) (and thus determine whose bankruptcy it is in the latter), which may be immediately adjacent in a text: (i) ACME, Inc., was actually doomed the moment Jorge Jimenez and 52 other employees were laid off without a warning.</Paragraph>
    <Paragraph position="1"> (ii) That bankruptcy was not, however, the last blow.</Paragraph>
    <Paragraph position="2"> As an example, we will sketch out the creation process of the BANKRUPTCY script. In Section 2, we will describe the status of scripts in ontological semantics, and in Section 3 the format of their representation. Section 4 deals with the heuristics/discovery of the information that goes into a script, a sort of knowledge engineering, if you will. Section 5 presents the resulting script BANKRUPTCY, formatted to a certain grain size of the information discovered in Section 4. Section 6 touches briefly upon just a few of the problems script acquisitions poses.</Paragraph>
  </Section>
class="xml-element"></Paper>