<?xml version="1.0" standalone="yes"?>
<Paper uid="M92-1042">
  <Title>Set list for ATTEMPTED ATTACK : ESCAPED INJURY NO INJURY Set list for THREATENED ATTACK incidents : INJURY NO INJURY</Title>
  <Section position="2" start_page="0" end_page="0" type="metho">
    <SectionTitle>
2.0 DEFINITIONS OF SLOT TYPES
</SectionTitle>
    <Paragraph position="0"> 0 . MESSAGE: ID -- The first line of the message, e .g., DEV-MUC3-0001 (NOSC). This slot serves as an index and is not scored in its own right .</Paragraph>
    <Paragraph position="1"> 1. MESSAGE: TEMPLATE -- A number that distinguishes the templates for a give n message. In the answer key, the word OPTIONAL in parentheses after th e template number indicates that there is significant doubt whether the inciden t belongs in the database .</Paragraph>
    <Paragraph position="2"> 2. INCIDENT: DATE -- The date of incident (according to local time, not Greenwich Mean Time) .</Paragraph>
    <Paragraph position="3"> 3. INCIDENT: LOCATION -- The place where the incident occurred .</Paragraph>
    <Paragraph position="4"> 4. INCIDENT: TYPE -- A terrorist act reported on in the message .</Paragraph>
    <Paragraph position="5"> 5. INCIDENT : STAGE OF EXECUTION -- An indicator of whether the terrorist act wa s accomplished, attempted, or merely threatened .</Paragraph>
    <Paragraph position="6"> 6. INCIDENT: INSTRUMENT ID -- A device used by the perpetrator(s) in carryin g out the terrorist act.</Paragraph>
    <Paragraph position="7"> 7. INCIDENT: INSTRUMENT TYPE -- The category that the instrument fits into . 8. PERP: INCIDENT CATEGORY -- The subcategory of terrorism that the inciden t fits into, as determined by the nature of the perpetrators .</Paragraph>
    <Paragraph position="8"> 9. PERP: INDIVIDUAL ID -- A person responsible for the incident .</Paragraph>
    <Paragraph position="9"> 10. PERP: ORGANIZATION ID -- An organization responsible for the incident . 11. PERP: ORGANIZATION CONFIDENCE -- The way a perpetrator organization i s viewed in the message.</Paragraph>
    <Paragraph position="10"> 12. PHYS TGT : ID -- A thing (inanimate object) that was attacked .</Paragraph>
    <Paragraph position="11"> 13. PHYS TGT: TYPE -- The category that the physical target fits into. 14. PHYS TGT: NUMBER -- The number of physical targets with a particular ID an d TYPE.</Paragraph>
    <Paragraph position="12"> 15. PHYS TGT : FOREIGN NATION -- The nationality of a physical target, if the nationality is identified in the article and if it's different from country where incident occurred .</Paragraph>
    <Paragraph position="13"> 16. PHYS TGT : EFFECT OF INCIDENT -- The impact of the incident on a physical target . 17. PHYS TGT : TOTAL NUMBER -- The total number of physical targets . 18. HUM TGT: NAME -- The name of a person who was the obvious or apparen t target of the attack or who became a victim of the attack .</Paragraph>
    <Paragraph position="14"> 19. HUM TGT: DESCRIPTION -- The title or role of a named human target or a general description of an unnamed human target .</Paragraph>
    <Paragraph position="15"> 20. HUM TGT : TYPE -- The category that the human target fits into .</Paragraph>
    <Paragraph position="16"> 21. HUM TGT: NUMBER -- The number of human targets with a particular NAME , DESCRIPTION, and TYPE.</Paragraph>
    <Paragraph position="17"> 22. HUM TGT: FOREIGN NATION -- The nationality of a human target, if th e nationality is identified in the article and if it's different from country wher e incident occurred.</Paragraph>
    <Paragraph position="18"> 23. HUM TGT: EFFECT OF INCIDENT -- The impact of the incident on a human target. 24. HUM TGT: TOTAL NUMBER -- The total number of human targets.</Paragraph>
  </Section>
  <Section position="3" start_page="0" end_page="0" type="metho">
    <SectionTitle>
3.0 DEFINITIONS OF FILL TYPE S
</SectionTitle>
    <Paragraph position="0"> Set fill : An item from a finite list of possibilities enumerated in th e documentation provided to participants .</Paragraph>
    <Paragraph position="1"> Numeric : A number, a range of numbers, or a number with a prefix meanin g &amp;quot;approximately&amp;quot;.</Paragraph>
    <Paragraph position="2"> Text conversion : A canonical form extracted or derived from the text . The documentation provided to participants specifies the expected format . Text string : A string extracted from the text and placed inside double quotes in the slot. Note that this string may contain misspellings, if found in the original text . Null : A hyphen (-) indicating that the system has no response . Inapplicable : An asterisk (*) indicating that a particular slot is never to be filled in the case o f certain incident types .</Paragraph>
  </Section>
  <Section position="4" start_page="0" end_page="0" type="metho">
    <SectionTitle>
4.0 GENERAL REQUIREMENTS FOR FILL S
</SectionTitle>
    <Paragraph position="0"/>
    <Section position="1" start_page="0" end_page="0" type="sub_section">
      <SectionTitle>
4.1 Format for System Responses
</SectionTitle>
      <Paragraph position="0"> System responses should look like plain text, e .g., they cannot be enclosed i n parentheses, multi-word fillers cannot be connected by underscore characters, etc .</Paragraph>
      <Paragraph position="1"> Systems are not permitted to use the slash notation that is used in the key t o separate alternative forms of a single filler .</Paragraph>
      <Paragraph position="2"> When multiple fillers for a single slot are generated, each should appear on a separate line, arranged in a column, with space padding in front (no tabs) . Some slots require that their fillers be cross-referenced to the referent (i .e., the filler of some other slot). To match the answer sheet, this should be done by appending the referent, separating the two data items with a colon .</Paragraph>
      <Paragraph position="3"> Example fill for the PHYS TARGET : EFFECT OF INCIDENT slot, whose fillers must be cross-referenced to the corresponding fillers in the PHYS TGT : ID slot.</Paragraph>
    </Section>
  </Section>
  <Section position="5" start_page="0" end_page="7" type="metho">
    <SectionTitle>
PHYS TGT: ID
&amp;quot;OFFICES OF CITICORP BANK&amp;quot;
&amp;quot;RESIDENCE OF US AMBASSADOR&amp;quot;
PHYS TOT: EFFECT OF INCIDENT SOME DAMAGE: &amp;quot;OFFICES OF CITICORP BANK &amp;quot;
DESTROYED: &amp;quot;RESIDENCE OF US AMBASSADOR&amp;quot;
</SectionTitle>
    <Paragraph position="0"> One template form serves for all incident types . However, depending on th e incident type, one or more slots do not apply . These slots should appear with a n asterisk as the fill, and they will not figure in the scoring . For irrelevant articles, al l slots except the MESSAGE : ID slot should have an asterisk.</Paragraph>
    <Section position="1" start_page="0" end_page="7" type="sub_section">
      <SectionTitle>
4.2 Special Formats for Answer Keys
</SectionTitle>
      <Paragraph position="0"> All fills in the answer key will be in upper case .</Paragraph>
      <Paragraph position="1"> If there is more than one &amp;quot;correct&amp;quot; answer for any given slot filler, the option s will all appear on one line in the answer key, separated by a slash .</Paragraph>
      <Paragraph position="2"> The word OPTIONAL may appear in parentheses after the filler for the MESSAGE : TEMPLATE slot, indicating that generation of this template is optional .</Paragraph>
      <Paragraph position="3"> A question mark preceding a filler indicates that generation of this filler i s optional, i.e ., that null (hyphen) is also a correct system response .</Paragraph>
    </Section>
  </Section>
  <Section position="6" start_page="7" end_page="7" type="metho">
    <SectionTitle>
5.0 GENERAL GUIDELINES FOR GENERATING MORE THAN ON E
TEMPLATE PER ARTICL E
</SectionTitle>
    <Paragraph position="0"> If an article discusses more than one relevant type of terrorist incident, eac h such incident should be captured in a separate template .</Paragraph>
    <Paragraph position="1"> If an article discusses more than one instance of the same relevant type o f terrorist incident, each such incident should be captured in a separate template . A &amp;quot;separate instance&amp;quot; is one which has a different filler for the location, date, category , or perpetrator slot . If no distinctions of these kinds are made in the text, th e instances should be incorporated into a single template, e .g., if the article describe s &amp;quot;attacks&amp;quot; by &amp;quot;rebels&amp;quot; on &amp;quot;ten power stations&amp;quot; and does not give varying information on the location of those targets, etc. Note that the level of granularity is defined by what can go in a slot; thus, an article that describes two bombings on targets on different streets in the same neighborhood should be captured in one templat e rather than two, since the location slot cannot have a filler that is at the level o f granularity of a street.</Paragraph>
  </Section>
  <Section position="7" start_page="7" end_page="7" type="metho">
    <SectionTitle>
6.0 DATA TYPES FOR FILLERS
</SectionTitle>
    <Paragraph position="0"> The type of data that is to be generated for each of the slots is shown here .</Paragraph>
    <Paragraph position="1"> Section 7 contains information on which slots can be null, which slots ar e inapplicable for particular incident types, and which slots can contain multipl e  values .</Paragraph>
    <Paragraph position="2"> 0. MESSAGE:ID 1. MESSAGE: TEMPLATE 2. INCIDENT : DATE 3. INCIDENT: LOCATION 4. INCIDENT : TYPE 5 . INCIDENT : STAGE OF EXECUTION 6. INCIDENT : INSTRUMENT I D 7. INCIDENT: INSTRUMENT TYPE 8. PERP: INCIDENT CATEGORY 9. PERP: INDIVIDUAL I D 10. PERP: ORGANIZATION ID 11. PERP: ORGANIZATION CONFIDENCE 12. PHYS TGT: ID 13. PHYS TGT: TYPE 14. PHYS TGT: NUMBER 15. PHYS TGT: FOREIGN NATION 16. PHYS TGT: Lrrt;CT OF INCIDENT 17. PHYS TGT: TOTAL NUMBER 18. HUM TGT: NAME 19. HUM TGT: DESCRIPTIO N 20. HUM TGT: TYPE 21. HUM TGT: NUMBER 22. HUM TGT: FOREIGN NATION 23. HUM TGT: EFFECT OF INCIDENT 24. HUM TGT: TOTAL NUMBER  1) Ordering need not match answer sheet -- the scoring program will attempt t o make best match .</Paragraph>
    <Paragraph position="3"> 2) On the answer sheet, the word OPTIONAL in parentheses after the templat e number indicates that there is significant doubt whether the incident belongs in th e database .</Paragraph>
    <Paragraph position="4"> 7.3 Slot 2--INCIDENT: DATE Applicability : Applicable to all types of incidents Number of fillers: Always one filler per template, unless NO DATE appears i n the message header and a date cannot be determined from the body of the article, in which case NULL (hyphen) is appropriate. General method for filling : A form generated by the system from the text , expressed in one of the following forms (whichever is appropriate for the article) : 1. DD MMM YY (e .g. 21 JAN 89, meaning &amp;quot;on 21 JAN 89 &amp;quot;) 2. DD MMM YY - DD MMM YY (e .g. 15 JAN 89 - 21 JAN 89, meaning &amp;quot;on or between 15 JAN 89 and 21 JAN 89&amp;quot; ) 3. - DD MMM YY (e .g. - 21 JAN 89, meaning &amp;quot;on or before 21 JAN 89&amp;quot;) Notes : 1) If the article contains the name of a day of the week, e .g. &amp;quot;last Wednesday&amp;quot; ,  rather than a reference to the date, use form 3, above, with the best known absolute date as the anchor, e.g., the date of the article . 2) If the article uses an easily calculable expression such as &amp;quot;yesterday,&amp;quot; us e form 1, above, with the date calculated from the best known absolute date as th e anchor, e.g., the date of the article . An &amp;quot;easily calculable&amp;quot; expression is one tha t indicates how many days to add or subtract from the anchor . 3) Whenever the date for an event is derived by default from the date in th e message header, the answer key will use form 3, above, with the header date as th e anchor .</Paragraph>
    <Section position="1" start_page="7" end_page="7" type="sub_section">
      <SectionTitle>
7.4 Slot 3--INCIDENT: LOCATIO N
</SectionTitle>
      <Paragraph position="0"> Applicability : Applicable to all types of incidents Number of fillers : Always one (possibly complex) filler per templat e General method for filling : The country where the incident occurred ma y be explicit in the text or may have to be inferred .</Paragraph>
      <Paragraph position="1"> When further information is  available about the location, give the names in order of increasing specificity , separated by a colon, and put the location type in parentheses after each name .  than specifically in that place .</Paragraph>
      <Paragraph position="2"> 2) The incident may have occurred between two named places, in which cas e use a dash to separate them .</Paragraph>
      <Paragraph position="3"> Example : COLOMBIA: CUCUTA (CITY) - CAMPANARIO (REGION ) 3) If the article says the specific location is unknown, just put the more general location(s) .</Paragraph>
      <Paragraph position="4"> 4) Do not provide specific place name information if the message is unclear as to whether that place is the location of the incident or the location of the reporting of the incident (or some other location).</Paragraph>
      <Paragraph position="5"> 5) This slot should never be left blank. Always put at least the country name , even if it must be inferred . The country where the article originated is not always a  attack. It is not clear from the article whether the fire was set as an act of arson or whether it resulted from an explosion .</Paragraph>
      <Paragraph position="6"> 2) Various kinds of rifles, including assault rifles, fit in the category of RIFLE . 3) The supercategory of EXPLOSIVE includes a mixture of explosive devices an d explosive materials .</Paragraph>
      <Paragraph position="7"> 4) DYNAMITE includes dynamite in any of its various forms, including sticks , gel, etc.</Paragraph>
      <Paragraph position="8">  perpetrator is a member of the government/military/police . 3) This slot may be filled even if the perpetrators are not identified, if the tex t gives strong evidence for the category without providing any strings to fill the perpetrator slots ; however, it will generally be the case that this slot is null if th e perpetrator slots are null .</Paragraph>
      <Paragraph position="9">  1) Use REPORTED AS FACT as a default if the identity of the perpetrator org an d its responsibility for the incident appear not to be in question . 2) Use SUSPECTED OR ACCUSED if the article explicitly expresses some degree o f  uncertainty about the identity of the perpetrator org, e.g., by use of qualifying words. This fill should also be used if the article's reporting rests on suspicions o r accusations expressed by some source cited by the article's originator or by th e article's originator himself.</Paragraph>
    </Section>
  </Section>
  <Section position="8" start_page="7" end_page="7" type="metho">
    <SectionTitle>
3) Use SUSPECTED OR ACCUSED BY AUTHORITIES instead of SUSPECTED OR ACCUSED
</SectionTitle>
    <Paragraph position="0"> for cases where the article is conveying the information that the government , military, police, or other authority figure is expressing the suspicion/accusation o r is accepting/admitting guilt on behalf of another authority that has been identifie d as the perpetrator org . (In the latter case, where the perpetrator is himself a n authority figure, use CLAIMED OR ADMITTED if he admits/claims his own org 's guilt.) 4) Use POSSIBLE if an article mentions an organization in the context of th e incident without actually accusing that organization of being responsible for it .</Paragraph>
    <Paragraph position="1"> 7 .13 Slot 12--PHYS TGT : ID Applicability : Not applicable to KIDNAPPING incidents Number of fillers: Null, or one or more fillers .</Paragraph>
    <Paragraph position="2"> Note : Use this slot for the entities that are the targets of incidents (facilities , buildings, vehicles, etc.), not for whatever parts happened to have been damaged as a result of the incident (e .g., &amp;quot;windows&amp;quot;) unless the text doesn't mention the entity (target) that they are part of.</Paragraph>
    <Paragraph position="3"> 7.14 Slot 13--PHYS TGT : TYPE Applicability : Not applicable KIDNAPPING incidents Number of fillers : Null if ID slot null, or one filler per filler in ID slot . Cross-referencing : Include cross-reference to PHYS TGT : ID Set list:</Paragraph>
  </Section>
  <Section position="9" start_page="7" end_page="7" type="metho">
    <SectionTitle>
CIVILIAN RESIDENCE
COMMERCIAL
COMMUNICATIONS
DIPLOMAT OFFICE OR RESIDENCE
ENERGY
FINANCIAL
GOVERNMENT OFFICE OR RESIDENCE
LAW ENFORCEMENT FACILITY
POLITICAL FIGURE OFFICE OR RESIDENCE
ORGANIZATION OFFICE
TRANSPORT VEHICLE
TRANSPORTATION FACILITY
TRANSPORTATION ROUTE
WATER
OTHER
</SectionTitle>
    <Paragraph position="0"> one physical target .</Paragraph>
    <Paragraph position="1"> Otherwise, fill this slot with a digit generated by the syste m from the info available in the text .</Paragraph>
    <Paragraph position="2"> If the text indicates a range of values like &amp;quot;between 6 and 8&amp;quot; or &amp;quot;at least 6,&amp;quot; use a hyphen as an operator, making the fills &amp;quot;6-8 &amp;quot; A-10 and &amp;quot;6-&amp;quot;, respectively . If the text conveys an approximate number, as in &amp;quot;about 100&amp;quot; , use a tilde (-) as a prefix to the number .</Paragraph>
    <Paragraph position="3"> 7.16 Slot 15--PHYS TGT: FOREIGN NATIO N Applicability : Not applicable to KIDNAPPING incident s Number of fillers: Null if ID slot null, and null if country of location o f incident is same as nationality of target, else one filler if nationality is explicitl y mentioned in the text .</Paragraph>
    <Paragraph position="4"> Cross-referencing : Include cross-reference to PHYS TGT: ID.</Paragraph>
    <Paragraph position="5"> Set list : See separate file called set-list-foreign-nation .</Paragraph>
    <Paragraph position="6"> Example : The fill (disregarding cross-reference) should be HONDURAS if th e incident occurred in a country other than Honduras and if the physical target is the Honduran embassy .</Paragraph>
    <Paragraph position="7"> Note : The list, in principle, could be extended to contain all the countries of the world. However, it should be the case that it already includes at least all the possibilities covered by the MUC corpus .</Paragraph>
    <Paragraph position="8"> 7.17 Slot 16--PHYS TGT : EFFECT OF INCIDEN T Applicability : Not applicable to KIDNAPPING incidents Number of fillers : Null, or one or more fillers . The EFFECT slot may be filled in even if the ID/NUMBER/TYPE slots are all null (in the case where the articl e makes no direction mention of the target but rather refers to it indirectly by sayin g something in summary about damage) . Conversely, the EFFECT slot may be null even if the ID/NUMBER/TYPE slots are filled .</Paragraph>
    <Paragraph position="9"> Cross-referencing : Include cross-reference to PHYS TGT : ID ; if that slot is null , generate a dummy cross-reference, e .g., NO DAMAGE : &amp;quot;-&amp;quot;. Set list:</Paragraph>
  </Section>
  <Section position="10" start_page="7" end_page="7" type="metho">
    <SectionTitle>
DESTROYED
SOME DAMAGE
NO DAMAGE
</SectionTitle>
    <Paragraph position="0"> Additional set list items for ROBBERY incidents :</Paragraph>
  </Section>
  <Section position="11" start_page="7" end_page="7" type="metho">
    <SectionTitle>
MONEY TAKEN FROM TARGET
PROPERTY TAKEN FROM TARGET
TARGET TAKEN
</SectionTitle>
    <Paragraph position="0"> TGT: ID (in order to prevent the filler for this slot from being redundant with th e information contained in PHYS TGT : NUMBER) and only if an actual total numbe r value is given in the text.</Paragraph>
    <Paragraph position="1"> A-11 2) To fill this slot, use a digit generated by the system from the info available i n the text. If the text gives a range of values like &amp;quot;between 6 and 8&amp;quot; or &amp;quot;at least 6,&amp;quot; use a hyphen as an operator, making the fills &amp;quot;6-8&amp;quot; and &amp;quot;6-&amp;quot;, respectively . If the text conveys an approximate number, as in &amp;quot; about 10 pylons and power lines &amp;quot; , use a tilde (--) as a prefix to the number.</Paragraph>
    <Paragraph position="2">  Number of fillers : Null, or one or more filler s Cross-referencing : Include cross-reference to HUM TGT : NAME unless HUM TGT: NAME is null.</Paragraph>
    <Paragraph position="3"> Note : If the filler for this slot refers to a named person in the HUM TGT : NAME slot, this slot should be filled with a &amp;quot;title&amp;quot; (e .g., &amp;quot;Monsignor&amp;quot;, &amp;quot;Mr.&amp;quot;) or &amp;quot;role&amp;quot; (e.g., &amp;quot;engineer&amp;quot;, &amp;quot;priest&amp;quot;). It should be null if no title or role is given in the text (e .g., if only a general descriptor such as &amp;quot;woman&amp;quot; or &amp;quot;peasant&amp;quot; is present in the text) . 7.21 Slot 20--HUM TGT : TYPE Applicability : Applicable to all types of incidents.</Paragraph>
    <Paragraph position="4"> Number of fillers : Null if both NAME and DESCRIPTION slots are null ; else one filler per filler in NAME or DESCRIPTION slot (see cross-referencing instructions) . Cross-referencing : Include cross-reference to NAME slot if NAME slot is no t NULL; else include cross-reference to DESCRIPTION slot.</Paragraph>
    <Paragraph position="5"> Set list:</Paragraph>
  </Section>
  <Section position="12" start_page="7" end_page="7" type="metho">
    <SectionTitle>
CIVILIAN
DIPLOMAT
GOVERNMENT OFFICIAL
FORMER GOVERNMENT OFFICIAL
FORMER ACTIVE MILITARY
LEGAL OR JUDICIAL
ACTIVE MILITARY
POLITICAL FIGURE
</SectionTitle>
    <Paragraph position="0"> one human target. Otherwise, fill this slot with a digit generated by the system fro m the info available in the text . If the text indicates a range of values like &amp;quot;between 6 and 8&amp;quot; or &amp;quot;at least 6,&amp;quot; use a hyphen as an operator, making the fills &amp;quot;6-8&amp;quot; and &amp;quot;6-&amp;quot; , respectively. If the text conveys an approximate number, as in &amp;quot;about 10 student s and teachers&amp;quot;, use a tilde (-) as a prefix to the number.</Paragraph>
    <Paragraph position="1"> 7.23 Slot 22--HUM TGT: FOREIGN NATION Applicability : Applicable to all types of incidents Number of fillers: Null if both NAME and DESCRIPTION slots null, and null i f country of location of incident is same as nationality of target, else one filler pe r NAME/DESCRIPTION (see cross-referencing instructions) if nationality is explicitly mentioned in the text .</Paragraph>
    <Paragraph position="2"> Cross-referencing : Include cross-reference to NAME slot if NAME slot is no t NULL; else include cross-reference to DESCRIPTION slot .</Paragraph>
    <Paragraph position="3"> Set list: See separate file called set-list-foreign-nation .</Paragraph>
    <Paragraph position="4"> Example : The fill (disregarding cross-reference) should be HONDURAS if th e incident occurred in a country other than Honduras and if the human target i s Honduran embassy employees .</Paragraph>
    <Paragraph position="5"> Note : The list, in principle, could be extended to contain all the countries of th e world. However, it should be the case that it already includes at least all the possibilities covered by the MUC corpus .</Paragraph>
    <Paragraph position="6"> 7.24 Slot 23--HUM TGT : EFFECT OF INCIDENT Applicability : Applicable to all types of incidents .</Paragraph>
    <Paragraph position="7"> Number of fillers : Null, or one or more fillers . The EFFECT slot may be filled in even if the NAME/DESCRIPTION/NUMBER/TYPE slots are all null (in the case wher e the article makes no mention at all of any human targets or unwitting victims bu t says something in summary about (lack of) victims). Conversely, the EFFECT slot may be null even if the NAME/NUMBER/TYPE slots are filled.</Paragraph>
    <Paragraph position="8"> Cross-referencing : Include cross-reference to NAME slot if NAME slot is no t NULL; else include cross-reference to DESCRIPTION slot . If both slots are null , generate a dummy cross-reference, e .g., NO INJURY : &amp;quot;-&amp;quot;.</Paragraph>
    <Paragraph position="9"> Set list for all incidents except KIDNAPPING, ATTEMPTED ATTACK, an d</Paragraph>
  </Section>
  <Section position="13" start_page="7" end_page="7" type="metho">
    <SectionTitle>
THREATENED ATTACK incidents:
INJURY
DEATH
NO INJURY
NO DEATH
NO INJURY OR DEATH
</SectionTitle>
    <Paragraph position="0"> Set list for KIDNAPPING incidents, in addition to above list :</Paragraph>
  </Section>
  <Section position="14" start_page="7" end_page="7" type="metho">
    <SectionTitle>
REGAINED FREEDOM
</SectionTitle>
    <Paragraph position="0"> human target, i .e., when the number of fillers for NAME and DESCRIPTION sum up t o at least two (in order to prevent the filler for this slot from being redundant with the information contained in HUM TGT: NUMBER) and only if an actual total numbe r value is given in the text.</Paragraph>
    <Paragraph position="1"> 2) To fill this slot, use a digit generated by the system from the info available in the text. If the text gives a range of values like &amp;quot;between 6 and 8&amp;quot; or &amp;quot;at least 6,&amp;quot; use a hyphen as an operator, making the fills &amp;quot;6-8&amp;quot; and &amp;quot;6-&amp;quot;, respectively . If the tex t conveys an approximate number, as in &amp;quot;about 10 students and teachers&amp;quot;, use a tild e (--) as a prefix to the number.</Paragraph>
  </Section>
class="xml-element"></Paper>