Benjamin Aw
Add updated pkl file v3
6fa4bc9
raw
history blame contribute delete
No virus
17.3 kB
{
"paper_id": "M93-1033",
"header": {
"generated_with": "S2ORC 1.0.0",
"date_generated": "2023-01-19T03:14:32.123112Z"
},
"title": "APPENDIX A : SYSTEM WALKTHROUGH REFERENCE MATERIAL S",
"authors": [],
"year": "",
"venue": null,
"identifiers": {},
"abstract": "",
"pdf_parse": {
"paper_id": "M93-1033",
"_pdf_hash": "",
"abstract": [],
"body_text": [
{
"text": "(3) Explain how your system captured the GRANULARITY information for \"The company's latest stepper . \"",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "(4) I low does your system determine EQUIPMENT_TYPE for \"the new stepper\"? and for \"the company's latest stepper\" ? < A fa -0002-1 > <ar 7`7u VI -0002-2> ._ r t 'A a . <-0002-2 > Fh : (-<X. T 4 T 4 --0002-5> ) (-<1 . y T 4 -7-d --0002-4> ) (-T 4 5-4 --0002-3> ) <* n El -0002-1> : _ J, ;( : 850 1",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "Article 0002 is interesting because the text can be interpreted in more than one way in determining the number of tic ups . The key template lists only two tie-ups, as follows : In the case of b) above, a \"common sense\" reading of the text would probably argue that separate tie-up agreements are planned between Nisshin Kasai and Yamaichi, and between Douwa Kasai and Yamaichi . However, there is no clear textual evidence to support this interpretation completely over the interpretation where all three companies tie u p together. Therefore, in the case of b) above, the analysts felt that the best interpretation was to instantiate a single tieup, since there is no explicit linguistic evidence in the text to indicate that these were separate tie-ups.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "TIE-UPS",
"sec_num": null
},
{
"text": "a",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "TIE-UPS",
"sec_num": null
},
{
"text": "(1) How does your system determine whether there is a reportable tie-up ?",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "TIE-UPS",
"sec_num": null
},
{
"text": "(2) In Article 0002, how many tie-ups were found? What strategies are used to determine the number of tie-ups in Sentence 2 ?",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "TIE-UPS",
"sec_num": null
},
{
"text": "(3) How does your system determine the entities in a tie-up?",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "ENTITIES",
"sec_num": null
},
{
"text": "(4) How many discourse entities were identified anywhere in the text, and how did the system determine which of thes e were reportable? (9) Discuss any specific analysis your system does to handle teens like \"ryousha\", which appears in Sentence 2. How does your system deal with the usage of the particle \"no\" that precedes it ?",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "ENTITIES",
"sec_num": null
}
],
"back_matter": [
{
"text": "tl AA-C .at. at) .</TXT > </doc > \u2022 < g -000452-1 > -000452-1> : = 31 -7_j : < 1 :/ 7' 4 -j-4 --000452-1>",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "annex",
"sec_num": null
},
{
"text": "<T / 7-4 -i-4 --000452-2 > '\u2022 6` Y, r1 : CVD k 4k 7R ~J JI7 \u25ba",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Key Template",
"sec_num": "4.2"
}
],
"bib_entries": {
"BIBREF0": {
"ref_id": "b0",
"title": "How does the system determine the existence of a reportable microelectronics capability ?",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "How does the system determine the existence of a reportable microelectronics capability ?",
"links": null
},
"BIBREF1": {
"ref_id": "b1",
"title": "Three entities are mentioned in this article . How did your system determine which were involved in the ME capability? (If the joint venture company was not selected, was it rejected because its activity was in the future",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Three entities are mentioned in this article . How did your system determine which were involved in the ME capability? (If the joint venture company was not selected, was it rejected because its activity was in the future, or som e other basis?)",
"links": null
},
"BIBREF2": {
"ref_id": "b2",
"title": "How does the system identify company names? How does it associate locations with entities ?",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "How does the system identify company names? How does it associate locations with entities ?",
"links": null
},
"BIBREF3": {
"ref_id": "b3",
"title": "How does your system associate film type with each ME capability? (In this article \"CVD\" is immediately precede d by \"metal film",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "How does your system associate film type with each ME capability? (In this article \"CVD\" is immediately precede d by \"metal film .\" Will your present strategy allow more remote references? )",
"links": null
},
"BIBREF4": {
"ref_id": "b4",
"title": "How does you system determine the existence of reportable equipment? How is equipment type determined? (Woul d the determination of a new equipment type generate a new ME capability?)",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "How does you system determine the existence of reportable equipment? How is equipment type determined? (Woul d the determination of a new equipment type generate a new ME capability?)",
"links": null
}
},
"ref_entries": {
"FIGREF0": {
"num": null,
"uris": null,
"type_str": "figure",
"text": "4 r 4-f\u20ac1f;; : <1. r 4 r -t -11f,-0002-2 > < It -0002-1> : = A UM : Itt ifk Ti q r1'n \u2022 +)--t : (63 \"f f' ; r fig t-to fi'~ z t~' r tA : (63 \" : : RI at-3 < . A -1-\" ) 7t / 1`: \"6371 ; MIN : ; ;L`' 9' Ta . \" Irk 7$ b -0002-1> : _ Alt : <Alt -0002-1 > Jj PIT : (-<1 >' 7' 4 7' 4 --0002-2> ) (-<x ;-4 7-4 --0002-1> ) t;7~\u25ba>"
},
"FIGREF1": {
"num": null,
"uris": null,
"type_str": "figure",
"text": ") between Toukyou Kaijou Kasai Hoken and Daiwa Shouken , b) between Nisshin Kasai Kaijou Hoken, Douwa Kasai Kaijou Hoken and Yamaichi Shouken ."
},
"FIGREF2": {
"num": null,
"uris": null,
"type_str": "figure",
"text": "Explain any difficulties you had in identifying the following : a) the correct number of reportable entities b) the correct number of tie-ups (correct, for the sake of this walk-through allows BOTH interpretation s described in b) above, even though the key template does not . ) c) the correct links between reportable entities and reportable tie-ups . (6) How does your system determine aliases for entities ? (7) What problems were there in detecting the alias for the ENTITY named Toukyou Kaijou Kasai Hoken ? OTHER SPECIFIC QUESTIONS ABOUT THE ARTICL E (8) Sentence 2 ends with a general statement about products developed in tie-ups between insurance companies an d securities companies. How would your system determine that this is a generic, not a specific reference ?"
},
"TABREF0": {
"num": null,
"html": null,
"type_str": "table",
"content": "<table><tr><td colspan=\"2\">&lt;ACTIVITY-0592-1&gt; : = INDUSTRY: &lt;INDUSTRY-0592-1 &gt; 2.2 Key Template</td></tr><tr><td colspan=\"2\">&lt;TEMPLATE-0592-1&gt; := DOC NR : 0592 DOC DATE : 241189 DOCUMENT SOURCE : \"Jiji Press Ltd . \" CONTENT : &lt;TIE_UPRELATIONSHIP-0592-1 &gt; DATE TEMPLATE COMPLETED : 25119 2 EXTRACTION TIME: 0 COMMENT: / \"TOOL_VERSION : HUME .7.1 .def.def' / \"FILLRULES_VERSION: EJV .7.1 \" &lt;TIE_UP_RELATIONSHIP-0592-1&gt; : = ACTIVITY-SITE : (Taiwan (COUNTRY) &lt;ENTITY-0592-4&gt;) &lt;TEMPLATE-2789568-1&gt; : = START TIME : &lt;TIME-0592-1 &gt; DOC NR : 2789568 &lt;TIME-0592-1&gt; : = DOC DATE: 19109 0 DURING : 0190 DOCUMENT SOURCE: \"Comline Electronics \" &lt;OWNERSHIP-0592-1&gt; := CONTENT:&lt;MICROELECTRONICS_CAPABILITY-2789568-1 &gt; OWNED: &lt;ENTITY-0592-4&gt; &lt;MICROELECTRONICS_CAPABILITY-2789568-2&gt; TOTAL-CAPITALIZATION : 20000000 TWD DATE TEMPLATE COMPLETED : 031292 OWNERSHIP-% : (&lt;ENTITY-0592-3&gt; 10) EXTRACTION TIME: 7 (&lt;ENTITY-0592-2&gt; 15) COMMENT:/ \"TOOL_VERSION: LOCKE .5 .2.0 \" (&lt;ENTITY-0592-1&gt; 75) / \"FILLRULES_VERSION : EME.5 .2 .1 \"</td></tr><tr><td colspan=\"2\">TIE-UP STATUS : EXISTING ENTITY: &lt;ENTITY-0592-1 &gt; &lt;MICROELECTRONICS_CAPABILITY-2789568-1&gt; := 1 .3 QUESTIONS TO ADDRESS PROCESS : &lt;LITHOGRAPHY-2789568-1 &gt;</td></tr><tr><td colspan=\"2\">&lt;ENTITY-0592-2&gt; MANUFACTURER : &lt;ENTITY-2789568-1 &gt;</td></tr><tr><td colspan=\"2\">&lt;ENTITY-0592-3 &gt; 1. Coreference detennination &lt;MICROELECTRONICS_CAPABILITY-2789568-2&gt; : =</td></tr><tr><td colspan=\"2\">JOINT VENTURE CO: &lt;ENTITY-0592-4&gt; OWNERSHIP: &lt;OWNERSHIP-0592-1 &gt; ACTIVITY : &lt;ACTIVITY-0592-1 &gt; &lt;ENTITY-0592-1&gt; : _ NAME: BRIDGESTONE SPORTS CO ALIASES : \"BRIDGESTONE SPORTS \" \"BRIDGESTON SPORTS \" NATIONALITY : Japan (COUNTRY) TYPE : COMPANY ENTITY RELATIONSHIP: &lt;ENTITY_RELATIONSHIP-0592-1 &gt; &lt;ENTITY-0592-2&gt; : _ NAME: UNION PRECISION CASTING CO ALIASES : \"UNION PRECISION CASTING\" for: PROCESS : &lt;LITHOGRAPHY-2789568-2&gt; \"LOCAL CONCERN\" , MANUFACTURER: &lt;ENTITY-2789568-1 &gt; \"UNION PRECISION CASTING CO.' OF TAIWAN\" for: DISTRIBUTOR : &lt;ENTITY-2789568-1 &gt; \"A JAPANESE TRADING HOUSE\", &lt;ENTITY-2789568-1&gt; : = \"TAGA CO ., A COMPANY ACTIVE IN TRADING WITH TAIWAN\" for : NAME: Nikon COR P \"A JOINT VENTURE\", TYPE: COMPANY \"THE NEW COMPANY, BASED IN KAOHSIUNG, SOUTHERN TAIWAN\" , &lt;LITHOGRAPHY-2789568-1&gt; : _ \"THE JOINT VENTURE, BRIDGESTONE SPORTS TAIWAN CO.\" , TYPE: LASE R \"THE TAIWAN UNIT\" for : GRANULARITY : ( RESOLUTION 0.45 MI ) \"BRIDGESTONE SPORTS CO .\" , DEVICE : &lt;DEVICE-2789568-1 &gt; \"BRIDGESTON SPORTS\" , EQUIPMENT: &lt;EQUIPMENT-2789568-1 &gt; \"BRIDGESTONE SPORTS\" , &lt;LITHOGRAPHY-2789568-2&gt; : _ \"THE JAPANESE SPORTS GOODS MAKER \" TYPE : UNKNOWN</td></tr><tr><td colspan=\"2\">LOCATION: Taiwan (COUNTRY) GRANULARITY : ( RESOLUTION 0.5 MI )</td></tr><tr><td colspan=\"2\">NATIONALITY : Taiwan (COUNTRY ) EQUIPMENT: &lt;EQUIPMENT-2789568-2&gt;</td></tr><tr><td colspan=\"2\">TYPE: COMPANY &lt;DEVICE-2789568-1&gt; : =</td></tr><tr><td colspan=\"2\">ENTITY RELATIONSHIP: &lt;ENTITY_RELATIONSHIP-0592-1 &gt; FUNCTION: DRAM</td></tr><tr><td colspan=\"2\">&lt;ENTITY-0592-3&gt; := SIZE: (64 MBITS )</td></tr><tr><td colspan=\"2\">NAME : TAGA CO &lt;EQUIPMENT-2789568-I&gt; : _</td></tr><tr><td colspan=\"2\">NATIONALITY : Japan (COUNTRY) NAME_OR_MODEL : \"NSR-1755EX8A \" 2. EME</td></tr><tr><td colspan=\"2\">TYPE : COMPANY MANUFACTURER : &lt;ENTITY-2789568-1 &gt;</td></tr><tr><td colspan=\"2\">ENTITY RELATIONSHIP : &lt;ENTITY_RELATIONSHIP-0592-1 &gt; &lt;ENTITY-0592-4&gt; : = MODULES : &lt;EQUIPMENT-2789568-3 &gt; 2 .1 Text EQUIPMENT_TYPE: STEPPER</td></tr><tr><td colspan=\"2\">NAME : BRIDGESTONE SPORTS TAIWAN CO LOCATION: \"KAOHSIUNG\" (UNKNOWN) Taiwan (COUNTRY ) TYPE : COMPANY ENTITY RELATIONSHIP : &lt;ENTITY_RELATIONSHIP-0592-1 &gt; &lt;INDUSTRY-0592-1&gt; : = INDUSTRY-TYPE : PRODUCTION PRODUCT/SERVICE: (39 \"20,000 IRON AND METAL WOOD' [CLUBS]\" ) STATUS : IN_US E &lt;doc&gt; &lt;EQUIPMENT-2789568-2&gt; : = &lt;REFNO&gt; 000132038 &lt;/REFNO &gt; MANUFACTURER : &lt;ENTITY-2789568-1 &gt; &lt;DOCNO&gt; 2789568 &lt;/DOCNO&gt; EQUIPMENT_TYPE: STEPPER &lt;DD&gt; October 19, 1990 &lt;/DD&gt; STATUS : IN_US E &lt;SO&gt; Comline Electronics &lt;/SO&gt; &lt;EQUIPMENT-2789568-3&gt; : = &lt;TXT&gt; MANUFACTURER : &lt;ENTITY-2789568-1 &gt;</td></tr><tr><td colspan=\"2\">/ (39 \"GOLF [CLUBS]\" ) EQUIPMENT_TYPE : RADIATION SOURCE</td></tr><tr><td>STATUS : IN_US E</td><td>/ (39 \"GOLF [CLUBS] TO BE SHIPPED TO JAPAN\" )</td></tr><tr><td colspan=\"2\">&lt;ENTITY_RELATIONSHIP-0592-1&gt; :=</td></tr><tr><td colspan=\"2\">ENTITY 1 : &lt;ENTITY-0592-1 &gt; 2.3 Questions to Addres s</td></tr><tr><td/><td>&lt;ENTITY-0592-2&gt;</td></tr><tr><td/><td>&lt;ENTITY-0592-3&gt;</td></tr><tr><td colspan=\"2\">ENTITY2 : &lt;ENTITY-0592-4&gt;</td></tr><tr><td colspan=\"2\">REL OF ENTITY2 TO ENTITY I : CHILD</td></tr><tr><td colspan=\"2\">STATUS : CURRENT</td></tr><tr><td>&lt;/TXT&gt;</td><td/></tr><tr><td>&lt;/doc&gt;</td><td/></tr></table>",
"text": "Telex 2428134 COMLN J ."
},
"TABREF1": {
"num": null,
"html": null,
"type_str": "table",
"content": "<table><tr><td colspan=\"3\">3.2 Key Template</td><td/></tr><tr><td colspan=\"5\">-1 ? -A alPIr : \"M1 El In fI X11Th' 1 \" &lt;5-&gt; 7\u00b0I. -1-' -0002-1&gt; : = : 000 2 ?'(7}~B : 85010 8 3 . JJ V j : &lt;N M -0002-1 &gt; &lt;# -0002-2 &gt; 3 .1 Tex t &lt;doc &gt; fa : 01079 2 -T 411 B'f rB`1 : 6 0 &lt;#M fit -0002-1&gt; : =</td></tr><tr><td colspan=\"5\">&lt;REFNO&gt; g] 9 g rij .000002 &lt;/REFNO &gt; &lt;DOCNO&gt; 0002 &lt;/DOCNO &gt; &lt;DD&gt; 85 .01 .08 &lt;/DD &gt; J'44 -: &lt;x,/ 4 r 4 --0002-1 &gt; &lt;X. 7-4 4 --0002-2 &gt; tz 7&amp; . &lt; a&amp; fjj -0002-1 &gt; &lt;N M -0002-2&gt; : _</td></tr><tr><td>&lt;so&gt;</td><td colspan=\"4\">MEAN EH 8W 2</td><td>4 Pit ( \u00b1 3 9 6 r) &lt;/so&gt;</td></tr><tr><td>&lt;TXT &gt;</td><td/><td/><td/></tr><tr><td colspan=\"2\">Map rt .2. -7 :</td><td/><td colspan=\"2\">19MLt\" ttze r*&amp; \u00b1fit . Fif</td><td>ifa\u00b1tg Ro)Wft</td></tr><tr><td colspan=\"5\">-` W o)A3Y r.2 \u00b1d1, L'ilt ZfMt~' a# #A{~'f</td><td>, tcMljuAZ0DW -C t</td></tr><tr><td colspan=\"2\">tfao)Mk St</td><td/><td colspan=\"2\">itztca oDab, AMon-t. 056AM</td><td>at), 310*41o)r f</td></tr><tr><td colspan=\"4\">At-lXAh-r Z o)**o)I f l</td></tr><tr><td colspan=\"5\">eC b-Q-tz .H*M,*</td><td>A-ScC .,-Z M,</td><td>fUtz3r -*</td></tr><tr><td colspan=\"2\">o~z~</td><td colspan=\"3\">c~t~. i~tzt</td><td>+ Zijn7.L Atlz~i i\u20ac r1, 4\u00bb~:7~hH . 7:</td></tr><tr><td colspan=\"3\">-i-~e -Ti~~N</td><td>4</td><td>I ~\u2022#l.b~i~afid</td><td>+ ;~~~o~+' rar y . = t~A `~&lt;</td></tr><tr><td>/TXT &gt;</td><td/><td/><td/></tr><tr><td>&lt;/doc&gt;</td><td/><td/><td/><td>357</td></tr></table>",
"text": ""
}
}
}
}