<?xml version="1.0" standalone="yes"?>
<Paper uid="M91-1037">
  <Title>Set list for all incidents except DEATH THREAT, ATTEMPTED MURDER : INJUR Y DEATH NO INJUR Y NO DEATH NO INJURY OR DEATH Set list for KIDNAPPING incidents, in addition to above list : REGAINED FREEDOM Set list for ATTEMPTED MURDER: ESCAPED INJURY NO INJUR Y Set list for DEATH THREAT incidents : INJUR Y NO INJUR Y RESIGNATION (i .e., from job )</Title>
  <Section position="2" start_page="0" end_page="0" type="metho">
    <SectionTitle>
2.0 DEFINITIONS OF SLOT TYPE S
0 . MESSAGE ID -- The first line of the message, e .g., DEV-MUC3-0001 (NOSC).
</SectionTitle>
    <Paragraph position="0"> This slot serves as an index and is not scored in its own right .</Paragraph>
    <Paragraph position="1">  1. TEMPLATE ID -- A number that distinguishes the templates for a give n message . On the answer sheet, the word OPTIONAL in parentheses afte r the template number indicates that there is significant doubt whether th e incident belongs in the database .</Paragraph>
    <Paragraph position="2"> 2. DATE OF INCIDENT -- The date of incident (according to local time, no t Greenwich Mean Time) .</Paragraph>
    <Paragraph position="3"> 3. TYPE OF INCIDENT -- A terrorist act reported on in the message . 4. CATEGORY OF INCIDENT -- The subcategory of terrorism that the inciden t fits into .</Paragraph>
    <Paragraph position="4"> 5. PERPETRATOR : ID OF INDIV(S) -- The person(s) responsible for th e incident .</Paragraph>
    <Paragraph position="5"> 6. PERPETRATOR : ID OF ORG(S) --The organization responsible for th e inciden t 7. PERPETRATOR : CONFIDENCE  The way the perpetrator organization i s viewed in the message .</Paragraph>
    <Paragraph position="6">  8. PHYSICAL TARGET: ID(S) -- The thing(s) (inanimate object) that was/wer e attacked .</Paragraph>
    <Paragraph position="7"> 9. PHYSICAL TARGET : TOTAL NUM -- The total number of physical targets . 10. PHYSICAL TARGET : TYPE(S) -- The category that the physical target fit s into .</Paragraph>
    <Paragraph position="8"> 11. HUMAN TARGET : ID(S) -- The person(s) who was/were the obvious or apparent target(s) of the attack or who became victim(s) of the attack . 12. HUMAN TARGET: TOTAL NUM -- The total number of human targets . 13. HUMAN TARGET : TYPE(S) -- The category that the human target fits into . 14. TARGET : FOREIGN NATION(S) -- The nationality of the interests that were targeted, if identified in the article and if different from country wher e incident occurred .</Paragraph>
    <Paragraph position="9"> 15. INSTRUMENT : TYPE(S) -- The device used by the perpetrator(s) i n carrying out the terrorist act .</Paragraph>
    <Paragraph position="10"> 16. LOCATION OF INCIDENT -- The name of the country and specifi c geographic location where the incident occurred .</Paragraph>
    <Paragraph position="11">  documentation provided to participants specifies the expected format . Text string : A string extracted from the text and placed inside double quote s in the slot . ,Note that this string may contain misspellings, if found in the original text.</Paragraph>
    <Paragraph position="12"> Null : A hyphen (-) indicating that the system has no response .</Paragraph>
  </Section>
  <Section position="3" start_page="0" end_page="0" type="metho">
    <SectionTitle>
4.0 GENERAL REQUIREMENTS FOR FILLS
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) .</Paragraph>
    <Paragraph position="3"> 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 b y appending the referent, separating the two data items with a colon .</Paragraph>
    <Paragraph position="4"> Example fill for the EFFECT ON HUMAN TARGET slot, whose fillers must b e cross-referenced to the corresponding fillers in the HUMAN TARGET : ID(S) slot.</Paragraph>
    <Paragraph position="5"> (Note that the persons' roles have been omitted from the cross-reference .):</Paragraph>
  </Section>
  <Section position="4" start_page="0" end_page="0" type="metho">
    <SectionTitle>
HUMAN TARGET ID(S)
&amp;quot;HORACIO FERNANDEZ COTIELLO&amp;quot; (&amp;quot;LAWYER&amp;quot; )
&amp;quot;JORGE SAMUDIO&amp;quot; (&amp;quot;JUDGE&amp;quot; )
EFFECT ON HUMAN TARGET(S) DEATH : &amp;quot;HORACIO FERNANDEZ COTIELLO &amp;quot;
INJURY : &amp;quot;JORGE SAMUDIO &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 , all slots except the MESSAGE ID slot should have an asterisk .</Paragraph>
    <Paragraph position="1"> A--4</Paragraph>
  </Section>
  <Section position="5" start_page="0" end_page="0" type="metho">
    <SectionTitle>
4.2 SPECIAL FORMATS FOR ANSWER KEY S
</SectionTitle>
    <Paragraph position="0"> All fills in the answer sheet will be in upper case . If there is more than on e &amp;quot;correct&amp;quot; answer for any given slot filler, the options will all appear on one line i n the answer sheet, separated by a slash . The word OPTIONAL may appear i n parentheses after the filler for the TEMPLATE ID, indicating that generation of thi s template is optional . A question mark preceding a filler indicates that generation of this filler is optional, i .e ., that null (hyphen) is also a correct system response .</Paragraph>
  </Section>
  <Section position="6" start_page="0" end_page="11" type="metho">
    <SectionTitle>
5 .0 GENERAL GUIDELINES FOR GENERATING MORE THAN ONE TEMPLAT E
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 . If an article discusse s more than one instance of the same relevant type of terrorist incident, each suc h incident should be captured in a separate template . A &amp;quot;separate instance&amp;quot; is on e which has a different filler for the location, date, category, or perpetrator slot . If no distinctions of these kinds are made in the text, the instances should b e incorporated into a single template, e .g ., if the article describes &amp;quot;attacks&amp;quot; b y &amp;quot;rebels&amp;quot; on &amp;quot;ten power stations&amp;quot; and does not give varying information on th e location of those targets, etc . Note that the level of granularity is defined by wha t 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>
    <Paragraph position="1">  1. TEMPLATE ID 2. DATE OF INCIDENT 3. TYPE OF INCIDENT 4. CATEGORY OF INCIDEN T 5. PERPETRATOR: ID OF INDIV(S) 6. PERPETRATOR : ID OF ORG(S ) 7. PERPETRATOR : CONFIDENCE 8. PHYSICAL TARGET : ID(S) 9. PHYSICAL TARGET : TOTAL NU M 10. PHYSICAL TARGET : TYPE(S )  HUMAN TARGET : ID(S) 12. HUMAN TARGET : TOTAL NUM 13. HUMAN TARGET : TYPE(S ) 14. TARGET: FOREIGN NATION(S ) 15. INSTRUMENT : TYPE(S ) 16. LOCATION OF INCIDENT 17. EFFECT ON PHYSICAL TARGET(S ) 18. EFFECT ON HUMAN TARGET(S)  1) Ordering need not match answer sheet -- the scoring program will mak e best match.</Paragraph>
    <Paragraph position="2"> 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 the database .</Paragraph>
    <Paragraph position="3"> 7.3 SLOT 2 -- DATE OF INCIDENT  Number of fillers : Always one filler per template, unless NO DATE appears in th e message header and a date cannot be determined from the body of the article, i n which case NULL (hyphen) is appropriate .</Paragraph>
    <Paragraph position="4"> 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) :  rather than a reference to the date, use form 3, above, with the best know n 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 a s A--6 the anchor, e.g., the date of the article . An &amp;quot;easily calculable&amp;quot; expression is one that indicates how many days to add or subtract from the anchor . 3) Whenever the date for an even t message header,' the answer key as the anchor.</Paragraph>
  </Section>
  <Section position="7" start_page="11" end_page="11" type="metho">
    <SectionTitle>
ARSON ATTEMPTED ARSON ARSON THREAT
MURDER ATTEMPTED MURDER DEATH THREAT
BOMBING ATTEMPTED BOMBING BOMB THREAT
KIDNAPPING ATTEMPTED KIDNAPPING KIDNAPPING THREAT
HIJACKING ATTEMPTED HIJACKING HIJACKING THREAT
ROBBERY ATTEMPTED ROBBERY ROBBERY THREAT
FORCED WORK ATTEMPTED FORCED WORK FORCED WORK STOPPAGE
STOPPAGE STOPPAGE THREAT
ATTACK ATTEMPTED ATTACK ATTACK THREAT
</SectionTitle>
    <Paragraph position="0"> The subcategory of STATE-SPONSORED VIOLENCE should be used when th e perpetrator is a member of the government/military/police .</Paragraph>
    <Paragraph position="1"> 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 fil l the perpetrator slots; however, it will generally be the case that this slot i s null if the perpetrator slots are null .</Paragraph>
    <Paragraph position="2">  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 .</Paragraph>
    <Paragraph position="3"> 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 rest s on suspicions or accusations expressed by some source cited by the article' s originator or by the article's originator himself .</Paragraph>
    <Paragraph position="4"> A--8 3) Use SUSPECTED OR ACCUSED BY AUTHORITIES instead of SUSPECTED O R ACCUSED for cases where the article is conveying the information that th e government, military, police, or other authority figure is expressing th e suspicion/accusation or is accepting/admitting guilt on behalf of anothe r authority that has been identified as the perpetrator org . (In the latter case , where the perpetrator is himself an authority figure, use CLAIMED O R  one physical target . Otherwise, fill this slot with a digit generated by the syste m from the info available in the text . If the text indicates a range of values lik e &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 .</Paragraph>
  </Section>
  <Section position="8" start_page="11" end_page="11" 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 FACILIT Y
TRANSPORTATION ROUTE
WATER
OTHER
</SectionTitle>
    <Paragraph position="0"> Number of fillers : Null, or one or more fillers Note : For incidents that have a physical target, the human target will tend to be some person or group that was at or near that target (either intentionally o r unintentionally) at the time of the incident . Anyone who suffers injury or death a s a result of the incident should definitely be mentioned in this slot .</Paragraph>
    <Paragraph position="1"> 7.13 SLOT 12 -- HUMAN TARGET: TOTAL NUM Applicability : Applicable to all types of incidents .</Paragraph>
    <Paragraph position="2"> Number of fillers: Null if ID null, else one filler Set list:</Paragraph>
  </Section>
  <Section position="9" start_page="11" end_page="11" type="metho">
    <SectionTitle>
PLURAL
</SectionTitle>
    <Paragraph position="0"> Note : Use PLURAL if the only information available is that there was more tha n one human target . Otherwise, fill this slot with a digit generated by the system from the info available in the text . If the text indicates a range of values lik e &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 .</Paragraph>
  </Section>
  <Section position="10" start_page="11" end_page="11" type="metho">
    <SectionTitle>
CIVILIAN
DIPLOMAT
GOVERNMENT OFFICIAL
FORMER GOVERNMENT OFFICIAL
FORMER ACTIVE MILITAR Y
LEGAL OR JUDICIA L
ACTIVE MILITAR Y
POLITICAL FIGURE
</SectionTitle>
    <Paragraph position="0"> described as being members of a military or police force .</Paragraph>
    <Paragraph position="1"> 7.15 SLOT 14 -- TARGET : FOREIGN NATION(S ) Applicability : Applicable to all types of incidents .</Paragraph>
    <Paragraph position="2"> Number of fillers : Null if country of location of incident is same as nationalit y of target, else one filler if nationality is explicitly mentioned in the text . Cross-referencing : Include cross-reference to PHYSICAL TARGET : ID(S) and/o r to HUMAN TARGET : ID(S).</Paragraph>
    <Paragraph position="3"> 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 i s the Honduran embassy and/or the human target is Honduran embassy employees . Set list: See separate file called set-list-foreign-nation .</Paragraph>
    <Paragraph position="4"> 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 th e possibilities covered by the MUC-3 corpus .</Paragraph>
    <Paragraph position="5">  General method for filling : The country where the incident occurred may b e explicit in the text or may have to be inferred . When further information i s 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 .  as BOMBING, do not imply damage .</Paragraph>
    <Paragraph position="6"> 7.19 SLOT 18 -- EFFECT ON HUMAN TARGET(S ) Applicability : Not applicable to MURDER incidents .</Paragraph>
    <Paragraph position="7"> Number of fillers : Null, or one or more fillers . The EFFECT slot may be filled i n even if the ID/NUMBER/TYPE slots are all null (in the case where the article make s no mention at all of any human targets or unwitting victims but says something i n summary about (lack of) victims) . Conversely, the EFFECT slot may be null even i f the ID/NUMBER/TYPE slots are filled .</Paragraph>
    <Paragraph position="8"> Cross-referencing : Include cross-reference to HUMAN TARGET : ID(S) ; if that slot is null, generate a dummy cross-reference, e .g., NO INJURY : &amp;quot;-&amp;quot;. Set list for all incidents except DEATH THREAT, ATTEMPTED MURDER :</Paragraph>
  </Section>
class="xml-element"></Paper>