<?xml version="1.0" standalone="yes"?>
<Paper uid="P98-1013">
  <Title>The Berkeley FrameNet Project</Title>
  <Section position="3" start_page="87" end_page="88" type="intro">
    <SectionTitle>
2 Organization and Workflow
</SectionTitle>
    <Paragraph position="0"/>
    <Section position="1" start_page="87" end_page="87" type="sub_section">
      <SectionTitle>
2.1 Overview
</SectionTitle>
      <Paragraph position="0"> The computational side of the FrameNet project is directed at efficiently capturing human insights into semantic structure. The majority of the work involved is marking text with semantic tags, specifying (again by hand) the structure of the frames to be treated, and writing dictionary-style entries based the results of annotation and a priori descriptions. With the exception of the example sentence extraction component, all the software modules are highly interactive and have substantial user interface requirements. Most of this functionality is provided by WWW-based programs written in PERL.</Paragraph>
      <Paragraph position="1"> Four processing steps are required produce the FrameNet database of frame semantic rep- null resentations: (a) generating initial descriptions of semantic and syntactic patterns for use in corpus queries and annotation (&amp;quot;Preparation&amp;quot;), (b) extracting good example sentences (&amp;quot;Sub null corpus Extraction&amp;quot;), (c) marking (by hand) the constituents of interest (&amp;quot;Annotation&amp;quot;), and (d) building a database of lexical semantic representations based on the annotations and other data (&amp;quot;Entry Writing&amp;quot;). These are discussed briefly below and shown in Fig. 3.</Paragraph>
    </Section>
    <Section position="2" start_page="87" end_page="88" type="sub_section">
      <SectionTitle>
2.2 Workflow and Personnel
</SectionTitle>
      <Paragraph position="0"> As work on the project has progressed, we have defined several explicit roles which project participants play in the various steps, these roles are referred to as Vanguard (1.1 in Fig. 3), Annotators (3.1) and Rearguard (4.1). These are purely functional designations: the same person may play different roles at different times. 9  1. Preparation. The Vanguard (1.1) pre- null pares the initial descriptions of frames, including lists of frames and frame elements, and adds these to the Frame Database (5.1) using the Frame Description tool (1.2). The Vanguard 90f course there are other staff members who write code and maintain the databases. This behind-thescenes work is not shown in Fig. 3.  also selects the major vocabulary items for the frame (the target words) and the syntactic patterns that need to be checked for each word, which are entered in the Lexical Database (5.2) by means of the Lexical Database Tool (1.3).</Paragraph>
    </Section>
  </Section>
class="xml-element"></Paper>