Benjamin Aw
Add updated pkl file v3
6fa4bc9
{
"paper_id": "M95-1027",
"header": {
"generated_with": "S2ORC 1.0.0",
"date_generated": "2023-01-19T03:12:54.687747Z"
},
"title": "",
"authors": [],
"year": "",
"venue": null,
"identifiers": {},
"abstract": "",
"pdf_parse": {
"paper_id": "M95-1027",
"_pdf_hash": "",
"abstract": [],
"body_text": [
{
"text": "This scenario concerns events that would be of interest to an analyst who tracks changes in company management . The event object captures the management post, the company, the current manager, and the reason why the post i s or will be vacant. The relational and low-level objects capture information on who's \"in\" and who's \"out,\" wher e the new manager came from, and where the old manager is going . A relevant article refers to assuming or vacating a post in a company and must minimally identify the post and either the person assuming the post or the perso n vacating the post .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "2 Template BN F <TEMPLATE> : = DOC_NR : \"NUMBER\"\u0108 ONTENT : <SUCCESSION_EVENT> * COMMENT :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "\"COMMENT\" -<SUCCESSION EVENT> : = SUCCESSION_ORG : <ORGANIZATION> A POST : \"POSITION TITLE\"I\"no title\" A /* string fill from text, or string \"no title\" (see fill rules) * / IN_AND_OUT : <IN_AND_OUT> + VACANCY_REASON :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "{DEPART_WORKFORCE, REASSIGNMENT, NEW_POST_CREATED , OTH_UNK} A COMMENT :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "\"COMMENT\" -<INAND OUT> : = IO_PERSON : <PERSON> A NEW_STATUS :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "{IN, IN_ACTING, OUT, OUT_ACTING} A ON_THE_JOB :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "{YES, NO, UNCLEAR} A OTHER_ORG : <ORGANIZATION> -REL_OTHER_ORG :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "{SAME_ORG, RELATED_ORG, OUTSIDE_ORG} -COMMENT :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "\"COMMENT\" -<ORGANIZATION> : _ ORG_NAME : \"NAME\" -ORG_ALIAS :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "\"ALIAS\" * ORG_DESCRIPTOR :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "\"DESCRIPTOR\" -ORG_TYPE :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "{GOVERNMENT, COMPANY, OTHER} A ORG_LOCALE : LOCALE-STRING {{LOC_TYPE}} * ORG_COUNTRY : NORMALIZED-COUNTRY-or-REGIO N COUNTRY-or-REGION STRING * COMMENT :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "\"COMMENT\" -<PERSON> : _ PER NAME : \"NAME\" A PER ALIAS :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "\"ALIAS\" * PER TITLE :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "\"TITLE\" * COMMENT :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "\"COMMENT\" -LOC_TYPE : :{CITY, PROVINCE, COUNTRY, REGION, UNK }",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "Note that each object defined by the template BNF contains a COMMENT slot . This slot is reserved for use in the answer-key templates ; it is not to be generated by the extraction systems . See Information Extraction Task Definition document for further information .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Fill Rule s",
"sec_num": "3"
},
{
"text": "DEFINITION : Top-level object.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".1 TEMPLATE Object",
"sec_num": "3"
},
{
"text": "See Information Extraction Task Definition for further information .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".1 TEMPLATE Object",
"sec_num": "3"
},
{
"text": "DEFINITION : Document identifier. See Information Extraction Task Definition for further information .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".1 DOC_NR Slot",
"sec_num": "3.1"
},
{
"text": "DEFINITION : Pointer to object that captures info on the management succession event . See Information Extraction Task Definition for general information .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".2 CONTENT Slo t",
"sec_num": "3.1"
},
{
"text": "Article must identify or refer to a company management post, must identify the company, and must identify either (1) the person who has assumed or will be assuming th e post or (2) the person who has vacated or will be vacating the post . To be relevant, it must be the case that the pos t definitely was, is now, or will be vacant ; if the vacancy is contingent on other events or the decision to replace an officer is otherwise not yet definite, the text is nonrelevant . In addition, in the case of condition (1), it is no t sufficient for a person to have been identified as a candidate for a post ; he or she must rather be identified as th e definite choice for that post, either on an acting or permanent basis . In the case of condition (2), any posts other than the person's most recently held one are not relevant ; thus, accounts of a person's prior work experience are not relevant . Similarly, any successions to a post other than the most recently reported succession to that post are no t relevant ; thus, accounts of people who held a particular post prior to the news of the most recent succession to tha t post are nonrelevant .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MINIMUM INSTANTIATION CONDITIONS :",
"sec_num": null
},
{
"text": "1. Relevant types of organizations are limited to those that are categorized as COMPANY in th e ORGANIZATION object . Thus, management posts in government entities, international agencies, and miscellaneous organizations such as labor unions are nonrelevant, whereas management posts in for-profi t and not-for-profit entities such as corporations, universities, and charitable organizations are relevant . 2. Relevant types of management posts are limited to company officers and other top management . Thus , positions such as university professor, law firm partner, and publishing company editor are nonrelevant , whereas positions such as university president and corporate treasurer are relevant . 3. Boards of directors are treated specially . Posts related to the chairmanship (chairman, vice chairman , deputy chairman, etc .) are relevant posts, as are directorships with special titles, such as 'managin g director' or 'director of the European subsidiary' (the latter may actually represent a separate usage of th e word 'director') . The general title of 'director' is taken to mean a general member of the board o f directors and is not relevant to the scenario .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "DEFINITION : The management succession event .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SUCCESSION_EVENT Object.",
"sec_num": "3.2"
},
{
"text": "See section 3 .1 .2 .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MINIMUM INSTANTIATION CONDITIONS :",
"sec_num": null
},
{
"text": "1. Since the simulated database design represented by the extraction template is centered on corporate post s rather than on persons, instantiate separate SUCCESSION_EVENT objects for each post, even in the cas e where a particular person is acquiring or vacating more than one post at a particular organization . 2. There will naturally be two SUCCESSION_EVENT objects involving a particular person if the person is giving up one post in order to take another. However, the text often does not clearly indicate that the person must give up the old post . In the unclear cases, the following guidelines are to be used : a. If the two posts are at the same company and are 'mutually exclusive', the person is giving u p the old post to acquire the new one . Examples of mutually exclusive posts : sole CEO versus co-CEO, chairman versus chairman emeritus, president versus vice-president . b. If the two posts are at the same company or at related companies (see section 3 .3 .5, below) and the posts are not mutually exclusive, the person is not giving up the old post to acquire the ne w one . (It is quite common for one person to hold several posts at one company, and it is no t uncommon for a person to hold posts in more than one company simultaneously if the companie s are related . ) c. If the two posts are at unrelated companies, the person is giving up the old post to acquire th e new one .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "3. All persons in a succession involving a shared post are represented in a single SUCCESSION_EVEN T object. The fact that a post is shared may be indicated by the title (e .g ., 'co-chairman'), but may also b e indicated indirectly . As a general guideline in these cases of indirect description, two persons ar e considered to share a post at a particular company if they are associated with exactly the same title an d with no differences in responsibilities . 4. A switch from a shared post, to a solely held post, or vice versa, is to be represented in separate SUCCESSION_EVENT objects, i .e ., a shared post is distinct from a solely held post .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "DEFINITION : Pointer to object that captures info on the organization with the (past, present, future ) management vacancy.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".2 .1 SUCCESSION_ORG Slo t",
"sec_num": "3"
},
{
"text": "The name or description of the organization must be given .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MINIMUM INSTANTIATION CONDITIONS :",
"sec_num": null
},
{
"text": "DEFINITION : The management post at SUCCESSION_ORG where there was, is, or will be a vacancy . MINIMUM INSTANTIATION CONDITIONS : Text must directly identify the management post, o r indirectly but clearly refer to a top management post .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".2 .2 POST Slot",
"sec_num": "3"
},
{
"text": "1. If the text provides a title or description of the post, the fill is a string containing that phrase, e .g ., \"CEO\" , \"chief executive officer\", \"chief executive\", \"the top office\", \"the top officer\", \"head\", \"president\" , \"presidency\", \"vice president, international marketing\", \"vice president in charge of internationa l marketing\" . Alternative fills will be provided in the answer key if the phrases found in the text ar e essentially equivalent, e .g ., \"CEO\", \"chief executive officer\" and \"chief executive\" . However, if the tex t provides a specific title and a more general job description, only the specific title will be included in th e answer key ; thus, if both \"chief executive officer\" and \"the top office\" appear in a text, the answer key wil l contain only \"chief executive officer\" . If the text provides only an indirect indication of a relevant post, e .g ., via a verb phrase such as \"will run the company\" or an idiom such as \"took the helm\", the fill is th e string \"no title\" . 2. The word 'post' and words that are essentially synonymous with it ('position', 'title', 'job', etc .) should be excluded from the fill . Thus, if the text string is \"the CEO post\", \"the position of CEO\", or \"the title CEO\" , the POST slot fill should be just \"CEO\" . 3. If a title is that of an acting officer, e .g ., \"acting president\", the title is treated as being the same as that of a permanent position . (The identification of acting officers is captured in the NEW_STATUS slot, rathe r than being represented at a higher level via separate SUCCESSION_EVENT objects .) Words such a s 'acting', 'interim' and 'temporary' should be excluded from the POST slot fill .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "DEFINITION : A pointer to the object that captures relational information on the person assuming a post and / or the person vacating that post . This slot will normally have one or two fills, but it may have three or more, in th e case of a shared post such as \"co-chairman\" or \"vice president\" .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".2.IN_AND_OUT Slo t",
"sec_num": "3"
},
{
"text": "The article must identify the person by name . SPECIAL USAGE NOTES : 1 . Instantiate separate IN_AND_OUT objects for each move, even when this results in the creation of identical IN_AND_OUT objects, as in the case where a particular person is acquiring or vacating more than one post at a particular organization .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MINIMUM INSTANTIATION CONDITIONS :",
"sec_num": null
},
{
"text": "DEFINITION : A general categorization of the reason why the post was, is, or will be vacant . When the outgoing person was/is occupying the post on an interim (acting) basis, the VACANCY_REASON refers not to th e acting titleholder's reason for departure but to the previous permanent titleholder's reason for departure . MINIMUM INSTANTIATION CONDITIONS : This slot must always be filled ; the default fill i s OTH_UNK .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".2.4 VACANCY_REASON Slo t",
"sec_num": "3"
},
{
"text": "1 . The categories that are to be used for this slot are defined as follows : DEPART_WORKFORCE --Vacancy created because of someone's retirement, death, or illness, o r because of someone resigning with intention not to work again . In the case of a retirement, th e DEPART_WORKFORCE fill should be used even if someone retires from one organization to go work a t another.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "REASSIGNMENT --Vacancy created because of someone's leaving a post voluntarily or involuntarily . The article must make some reference to the act of leaving, but does not have to indicate the reason fo r departure . Thus, it includes all positive evidence for the act of vacating a post (except for cases that fit th e definition of DEPART_WORKFORCE) : firing, resignation, quitting/leaving for any reason, moving to a ne w position at either the same company (e .g ., via promotion or management shuffle) or at a different company (jobhopping) .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "NEW_POST_CREATED --Vacancy exists because of creation of a new post at an existing company or a t a new company . When a new company is formed (including a company formed by a merger), all posts are new .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "OTH_UNK --Vacancy exists for other reasons or unknown reasons . The kinds of cases that fit thi s category with some frequency include (1) a post is being eliminated, and no positive evidence for the person' s act of relinquishing the post is given ; (2) a person is losing one but not all of his or her titles and not gainin g any new ones, and no positive evidence for the person's act of relinquishing the lost post is given ; (3) someon e is being 'succeeded' in a post or someone is a 'former' holder of a post, but no positive evidence for the person's act of departing is given ; (4) a company is being acquired by another company, but no positiv e evidence for people's act of departing the former company is given.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "The DEPART_WORKFORCE and NEW_POST_CREATED represent fairly specific reasons for a vacancy . REASSIGNMENT and OTH_UNK are more general categories . REASSIGNMENT would provid e an analyst only with the information that the article contained some specific reference to the person's departur e and/or move to a new job ; that reference may be enough to inform the analyst what the circumstances for the departure were.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "DEFINITION : This object relates information on the person assuming a post and/or the person vacating tha t post with information on his/her status vis-a-vis that post and his/her past or future corporate affiliation .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".IN_AND_OUT Object",
"sec_num": "3"
},
{
"text": "See section 3 .2 .3 .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MINIMUM INSTANTIATION CONDITIONS :",
"sec_num": null
},
{
"text": "DEFINITION : Pointer to object that captures info on the person assuming a post (or set of posts) or the person vacating that post (or same set of posts) . MINIMUM INSTANTIATION CONDITIONS : See section 3 .2 .3 .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".3.1 IO_PERSON Slot",
"sec_num": "3"
},
{
"text": "1 . There is at least one situation where a single person may appear both in the role of the person assuming a post and in the role of the person vacating the post : the person's job status may be changing from 'actin g to 'permanent,' which is recorded via distinct fills in the NEW_STATUS slot for the two IN_AND_OU T objects .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "DEFINITION : Identification of the new status of IO_PERSON with respect to POST, i .e ., an indication of whether the person being referred to is (or will be) the new holder of a post or whether he/she is (or will be) the ol d holder of the post .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".3.2 NEW_STATUS Slo t",
"sec_num": "3"
},
{
"text": "This slot must always be filled .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MINIMUM INSTANTIATION CONDITIONS :",
"sec_num": null
},
{
"text": "1 . The categories that are to be used for this slot are defined as follows :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "IN --The person's appointment is permanent.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "IN_ACTING --The person 's appointment is as an acting officer . OUT --The person is vacating the post . OUT_ACTING --The person is no longer going to be an acting officer . 2 . An 'acting' officer is one who is identified as \"acting\", \"temporary\", \"interim\", etc . or who is described as keeping the post only until a successor is found .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "DEFINITION : Identification of the status of IO_PERSON with respect to POST as of the date of the article, i .e., information on who the 'current' holder of the post was at the time the news appeared .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".3 ON_THE_JOB Slot",
"sec_num": "3.3"
},
{
"text": "This slot must always be filled . The default is UNCLEAR.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MINIMUM INSTANTIATION CONDITIONS :",
"sec_num": null
},
{
"text": "1 . The categories that are to be used for this slot are defined basically as follows, and their usage is describe d more fully in Appendix A : YES --The person held the post as of the date of the article . If the person is newly appointed to the job, YES means that the person is already actually onboard and working in that capacity ; if the person is vacating the post, YES means that the person has not yet been officially relieved of the duties of that post .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "NO --The person did not hold the post as of the date of the article . If the person is newly appointed to th e job, NO means that the person is not yet actually onboard and working in that capacity . If the person i s vacating the post, NO means that the person has already been officially relieved of the duties of that post .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "UNCLEAR --The information given in the article is not sufficient to determine whether the person hel d the post as of the date of the article . For example, the fill should be UNCLEAR if the article says that someon e was \"named\" to a post but does not say that the person has \"succeeded\" the predecessor (which would occasio n the fill to be YES) or that the person \"succeeds\" or \"will succeed\" the predecessor (which would occasion th e fill to be NO) .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "DEFINITION : Pointer to ORGANIZATION object that captures information on the IO_PERSON's past o r future employer organization . It indicates the past affiliation if the value of NEW_STATUS is IN or IN_ACTING, and it indicates the future affiliation if the value of ON_THE_JOB is NO . The organization may be of any type ; i t does not have to be type COMPANY .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".3.4 OTHER_ORG Slot",
"sec_num": "3"
},
{
"text": "The name or description of the organization must be given .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MINIMUM INSTANTIATION CONDITIONS :",
"sec_num": null
},
{
"text": "1. In the normal case, OTHER_ORG and SUCCESSION_ORG will point to the same ORGANIZATIO N object only when the succession event represents a promotion or shuffle within an organization . However, they may point to the same ORGANIZATION object under other circumstances as well, such as when a person holds more than one post and is going to give up some portion of them, but not all of them . 2. Unless the article makes it clear that someone is not moving directly from one job/company to another , assume that the transition is direct . For example, if an article says that an incoming person 'was' an office r at a different organization, assume that the person came directly from that organization, and fil l OTHER_ORG with a pointer to that organization . 3. Positions on a company's board of directors other than those that are relevant to the scenario (see Specia l",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "Usage Notes in section 3 .1 .2) are not considered jobs (employment) at that company . For this reason , OTHER_ORG will never point to an ORGANIZATION object that represents a board of directors . Furthermore, it will not point to the same ORGANIZATION object as the SUCCESSION_ORG slot if the person's only position at that organization is as a nonrelevant member of that organization's board . As a consequence, in cases where a new corporate officer was previously a director and in cases where a n outgoing corporate officer is going to be retaining or acquiring a seat on the board as a director, th e OTHER_ORG slot will point to the person's previous place of employment (when the person is a n incoming officer) or his next place of employment (when the person is an outgoing officer), if the tex t provides that information . Otherwise, leave the slot blank. (If there is obviously a major employment ga p between the person's stints at the two organizations, the OTHER_ORG fill may be marked optional in th e answer key. ) 4 . A consultant to a company is not an employee of the company . Therefore, the guidelines concernin g consultants are consistent with those outlined above concerning nonrelevant board members .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "DEFINITION : Identification of whether the person's new job and old job are with the same organization, a related organization, or an unrelated organization . In terms of the template definition, this slot indicates th e corporate relationship between OTHER_ORG and SUCCESSION_ORG .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".3.5 REL_OTHER_ORG Slo t",
"sec_num": "3"
},
{
"text": "This slot must be filled if OTHER_ORG is filled .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MINIMUM INSTANTIATION CONDITIONS :",
"sec_num": null
},
{
"text": "1 . The categories that are to be used for this slot are defined as follows :",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "SAME_ORG --The person's old and new positions are with the same organization . RELATED_ORG --The person's old and new positions are in organizations that are identified in the tex t as having some corporate relationship with each other, e .g., different units (child companies) of the same paren t company, different companies that have formed a merger, a company that is controlled via majority stoc k ownership by a different company .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "OUTSIDE_ORG --The person's old and new positions are in organizations that are not identified in th e text as having some corporate relationship with each other .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "SPECIAL USAGE NOTES :",
"sec_num": null
},
{
"text": "DEFINITION : An organization that is involved in the succession event . ",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".4 ORGANIZATION Objec t",
"sec_num": "3"
}
],
"back_matter": [
{
"text": "See Information Extraction Task Definition document for further information .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "annex",
"sec_num": null
},
{
"text": "DEFINITION : Alias for a person .See Information Extraction Task Definition document for further information .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".5.2 PER_ALIAS Slot",
"sec_num": "3"
},
{
"text": "DEFINITION : Title of a person .See Information Extraction Task Definition document for further information .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ".5.PER_TITLE Slot",
"sec_num": "3"
},
{
"text": "These are the main heuristics used by the annnotators in preparing the answer key fills for the ON_THE_JOB slot i n the IN_AND_OUT object.Al 99%-100% certainty : Fill is either YES or NO (no alternatives)A .1 .1 If NEW_STATUS = IN:A.1 .1 .1 YES :-if person is identified as currently holding pos t EXAMPLES : \"MR . X IS CEO \" \"Mr . Y (predecessor of Mr . X)'s subordinates would report temporaril y to MR . X (who therefore must be already on the job) \"if person is identified as having come on the job as of a date in the past (up to and including the date of th e article)EXAMPLES : \"MR . X TOOK OVER APRIL 1 \" \"MR . X WILL BE CEO, EFFECTIVE IMMEDIATELY \"if person is identifed as having been 'hired' (etc .) at least two months prior to the date of the article ; i n other words, it would be unreasonable to think the person was still in transitio n A.1 .1 .2 NO :-if all references to the situation are in the future tense and are not modified by a phrase referring to the date o f the article EXAMPLES : \"MR . X WILL REPORT to Mr . Y \" \"MR . -if potentially (but not necessarily) contradictory evidence is give n (e .g ., when different tenses are used in reference to the perso n acquiring the post ) EXAMPLE : 'named' plus 'will be involved '",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "APPENDIX A. ON_THE_JOB Slot Fill Criteria",
"sec_num": null
},
{
"text": "A.2 .2 .1 YES/UNCLEAR: -if there is genuine ambiguity in interpretation of a time modifier, an d maybe the article also makes it clear that the successor doesn't ye t hold the pos t EXAMPLES : \"In January, with Mr . Y a lame duck, ACTING CFO MR . X ran the search \" \"Mr . Y will assume post on March 1\" plus \"MR X IS MOVING TO TH E EAST COAST \"",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "A .2 .2 If NEW STATUS = OUT :",
"sec_num": null
},
{
"text": "-if all references to the person's position are in the past tense, bu t there is no concrete evidence, e .g ., of departure date from old pos t or arrival date at new post (if he has to give up old post before takin g on new one ) EXAMPLES : 'was', 'was previously '",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "A.2 .2 .2 NO/UNCLEAR :",
"sec_num": null
},
{
"text": "A .3 .1 If NEW_STATUS =IN :A .3 .1 .1 UNCLEAR :if past or present tense is used to relate the event, and if there are n o further indicator s EXAMPLES : 'named', 'approved the election of', 'succeeds' etc .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "A.3 50% certainty : Fill is UNCLEAR (no alternatives)",
"sec_num": null
},
{
"text": "A .3 .2 .1 UNCLEAR :if person retains another title, and if there are no indicators re th e title in question, and if there is no indication that the person is o n the job yet in some mutually exclusive pos t if a successor has been named to the post, but there is no indicatio n about the person represented by the current objec t if the person has 'resigned' or 'retired' or been 'fired,' 'ousted ' (etc .) , but no indication of the effective date is given",
"cite_spans": [
{
"start": 364,
"end": 408,
"text": "'retired' or been 'fired,' 'ousted ' (etc .)",
"ref_id": null
}
],
"ref_spans": [],
"eq_spans": [],
"section": "A .3 .2 If NEW STATUS = OUT :",
"sec_num": null
}
],
"bib_entries": {},
"ref_entries": {
"FIGREF0": {
"num": null,
"uris": null,
"type_str": "figure",
"text": "See section 3 .2 .1 ..4.1 ORG_NAME Slo t DEFINITION : The name of the organization . See Information Extraction Task Definition document for further information ."
},
"FIGREF1": {
"num": null,
"uris": null,
"type_str": "figure",
"text": "alias for an organization . See Information Extraction Task Definition document for further information ."
},
"FIGREF2": {
"num": null,
"uris": null,
"type_str": "figure",
"text": "describing an organization . See Information Extraction Task Definition document for further information ."
},
"FIGREF3": {
"num": null,
"uris": null,
"type_str": "figure",
"text": "type of organization . See Information Extraction Task Definition document for further information ."
},
"FIGREF4": {
"num": null,
"uris": null,
"type_str": "figure",
"text": "of an organization . See Information Extraction Task Definition document for further information ."
},
"FIGREF5": {
"num": null,
"uris": null,
"type_str": "figure",
"text": "where organization is located . See Information Extraction Task Definition document for further information . .5 PERSON Object DEFINITION : Person whose management post has changed or is changing . See Information Extraction Task Definition document for further information ."
},
"TABREF0": {
"num": null,
"text": "",
"content": "<table><tr><td colspan=\"2\">1 Narrative</td><td/></tr><tr><td/><td>(Version 1 .1, 18 Sep 95)</td><td/></tr><tr><td>1</td><td>Narrative</td><td>2</td></tr><tr><td/><td>Template BNF</td><td>2</td></tr><tr><td/><td>Fill Rules</td><td>2</td></tr><tr><td>.1</td><td>TEMPLATE Object</td><td>2</td></tr><tr><td>.1 .1</td><td>DOC_NR Slot</td><td>3</td></tr><tr><td>.1 .2</td><td>CONTENT Slot</td><td>3</td></tr><tr><td>.2</td><td>SUCCESSION_EVENT Object</td><td>3</td></tr><tr><td>.2 .1</td><td>SUCCESSION_ORG Slot</td><td>4</td></tr><tr><td>.2 .2</td><td>POST Slot</td><td>4</td></tr><tr><td>.2 .3</td><td>IN_AND_OUT Slot</td><td>4</td></tr><tr><td>.2 .4</td><td>VACANCY_REASON Slot</td><td>4</td></tr><tr><td>.3</td><td>IN_AND_OUT Object</td><td>5</td></tr><tr><td>.3 .1</td><td>IO_PERSON Slot</td><td>5</td></tr><tr><td>.3 .2</td><td>NEW_STATUS Slot</td><td>5</td></tr><tr><td>.3 .3</td><td>ON_THE_JOB Slot</td><td>6</td></tr><tr><td>.3 .4</td><td>OTHER_ORG Slot</td><td>6</td></tr><tr><td>.3 .5</td><td>REL_OTHER_ORG Slot</td><td>7</td></tr><tr><td>.4</td><td>ORGANIZATION Object</td><td>7</td></tr><tr><td>.4 .1</td><td>ORG_NAME Slot</td><td>7</td></tr><tr><td>.4 .2</td><td>ORG_ALIAS Slot</td><td>7</td></tr><tr><td>.4 .3</td><td>ORG_DESCRIPTOR Slot</td><td>7</td></tr><tr><td>.4 .4</td><td>ORG_TYPE Slot</td><td>7</td></tr><tr><td>.4 .5</td><td>ORG_LOCALE Slot</td><td>7</td></tr><tr><td>.4.6</td><td>ORG_COUNTRY Slot</td><td>7</td></tr><tr><td>.5</td><td>PERSON Object</td><td>7</td></tr><tr><td>.5 .1</td><td>PER_NAME Slot</td><td>7</td></tr><tr><td>.5 .2</td><td>PER_ALIAS Slot</td><td>8</td></tr><tr><td>.5 .3</td><td>PER_TITLE Slot</td><td>8</td></tr><tr><td colspan=\"2\">APPENDIX A . ON THE JOB Slot Fill Criteria</td><td>9</td></tr></table>",
"html": null,
"type_str": "table"
}
}
}
}