| { |
| "paper_id": "P82-1011", |
| "header": { |
| "generated_with": "S2ORC 1.0.0", |
| "date_generated": "2023-01-19T09:16:14.977548Z" |
| }, |
| "title": "Problems \u00a5ith Domain-Independent Natural Language Database Access Systems", |
| "authors": [ |
| { |
| "first": "Steven", |
| "middle": [ |
| "P" |
| ], |
| "last": "Shvartz", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Cognitive Systems Inc", |
| "location": { |
| "addrLine": "234 Church Street New Haven", |
| "region": "Ca" |
| } |
| }, |
| "email": "" |
| } |
| ], |
| "year": "", |
| "venue": null, |
| "identifiers": {}, |
| "abstract": "", |
| "pdf_parse": { |
| "paper_id": "P82-1011", |
| "_pdf_hash": "", |
| "abstract": [], |
| "body_text": [ |
| { |
| "text": "Zn the past decade, a number of natural language database access systems have been constructed (e.g. Hendrix 1976; Waltz et el. 1976; Sacerdoti 1978; Harris 1979; Lehner~ and Shwartz 1982; Shvartz 1982) . The level of performance achieved by natural language database access systems varies considerably, with the sore robust systems operating vithtn a narrow domain (i.e., content area) and relying heavily on domain-specific knowledge to guide the language understanding process. Transporting a system constructed for one domain into a new domain is extremely resource-intensive because a new set of domain-specific knowledge must be encoded.", |
| "cite_spans": [ |
| { |
| "start": 101, |
| "end": 114, |
| "text": "Hendrix 1976;", |
| "ref_id": "BIBREF2" |
| }, |
| { |
| "start": 115, |
| "end": 133, |
| "text": "Waltz et el. 1976;", |
| "ref_id": null |
| }, |
| { |
| "start": 134, |
| "end": 149, |
| "text": "Sacerdoti 1978;", |
| "ref_id": null |
| }, |
| { |
| "start": 150, |
| "end": 162, |
| "text": "Harris 1979;", |
| "ref_id": "BIBREF1" |
| }, |
| { |
| "start": 163, |
| "end": 188, |
| "text": "Lehner~ and Shwartz 1982;", |
| "ref_id": null |
| }, |
| { |
| "start": 189, |
| "end": 202, |
| "text": "Shvartz 1982)", |
| "ref_id": null |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "In order to reduce the cost of transportation, a great deal of current research has focussed on building natural language access systems that are domain-independent.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "More specifically, these systems attempt to use syntactic knowledge in con-~unction with knowledge about the structure of the database as a substitute for conceptual knowledge regarding the database content area. In this paper I examine the issue of whether or not it is possible to build a natural language database access systee that achieves an acceptable level of performance without including domain-specific conceptual knowledge. 6 gerforn=nca ~i~g~ion for oa~u\u00a3al language atoms= =X=~em=,", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "The principle motivation for building natural language systems for database access is ~o free the user from the need for data processing instruction. A natural language front end is a step above the \"English-like = query systems that presently dominate the commercial database retrieval field. English-like query systems allow the user to phrase requests as English sentences, but permit only a restricted subset of English and impose a rigid syntax on user requests. These English-like query systems are easy to learn, but a training period is still required for the user to learn to phrase requests that conform to ~hc~ restrictions.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "However, the training period is often very brief, and natura~ language systems can be considered superior only if no computer-related training or knowledge is required of the user.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "This criterion can only be met if no restrictions are placed on user queries. A user who has previously relied on a programmer-technician to code formal queries for information retrieval should be permitted to phrase inform%ion retrieval requests t~ the program in exactly the same way as to the technician. That is, whatever the technician would understand, the program should understand. For example, a natural language front end to a stock market database should understand that", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "(1) Did IBM go up yesterday? refers to PRZCE and not VOLUME. However, the system need not understand requests that a programmer-technician would be unable to process, e.g.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "(2) Is GENCO a likely takeover target?", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "That is, the programmer-technlcisn uorking for an investment firm would not be expected to know how t<) process requests that require \"expert\" knowledge and neither should | natural language front end, If, however, = natural language system cannot achieve the level of performance of a programear-technician it will seem stupid because it does not meet = user's expectations for an English understanding system, The mprograemer-technician criterion m cannot possibly be met by = domain-independent natural language access system because language understanding requires domain-specific world knowledge. On a theoretical level, the need for a knowledge base in a natural language processing system has been well-documented (e.g. Schank A Abelson 1977; Lehnert 1978; Dyer 1982 ). It will be argued below that in an applied context, a system that does not have a conceptual knowledge base can produce at best only a shallow level of understanding and one that does not meet the criterion specifled above. Further, the domain-independent approach creates a host of problems that are simply non-existent in knowledge-based s~stems.", |
| "cite_spans": [ |
| { |
| "start": 727, |
| "end": 749, |
| "text": "Schank A Abelson 1977;", |
| "ref_id": null |
| }, |
| { |
| "start": 750, |
| "end": 763, |
| "text": "Lehnert 1978;", |
| "ref_id": "BIBREF3" |
| }, |
| { |
| "start": 764, |
| "end": 773, |
| "text": "Dyer 1982", |
| "ref_id": "BIBREF0" |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "E~oble== far dolai0:i0dg~a0dan~ =~=~\u00ae=~ inference. ambiguity, sod aoagbora, Inferential processing is an integral part of natural language understanding. Consider the following requests from PEARL (Lehnert and Shvartz 1982; Shwartz 1982) when it operates in the domain of geological map generation:", |
| "cite_spans": [ |
| { |
| "start": 197, |
| "end": 223, |
| "text": "(Lehnert and Shvartz 1982;", |
| "ref_id": null |
| }, |
| { |
| "start": 224, |
| "end": 237, |
| "text": "Shwartz 1982)", |
| "ref_id": "BIBREF6" |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "(3) Show ss ell oil veils from 1970 to 1980. (4) Show Is all oil veils fro! 8000 ~ 7000. (5) Show se all oil wells 1 t~a 2000. (6) Show ee all oil wells 40 to 41, 80 to 81.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "A programmer-technician In the petrochemical industry would infer that (3) refers to drilling dates, (4) refers ~o veil depth, (5) refers ~o the sap scale, end (6) refers to latitude/longitude specifications. Correct processing of these requsst~ requires inferential processing that is based on knowledge of the petrochemical industry. That is, these conventions =re not in everyone's general working knowledge of the English language.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Yet they are standard usage for people who communicate with each other about drilling data, and any systss that claims t~o provide a natural language interface t~ l data base of drilling data must have the knowledge to correctly process requests such as these. Without such inferential processing, the user is required to spell out everything in detail, something that is sispty not necessary in normal English discourse.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Another probles for any natural language understanding systes is the processing of ambiguous words. In some cases disambiguation can be performed syntactically.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "In other cases, the structure of the database can provide the information necessary for word sense disambiguation (more on this below). However, in many cases disasbiguation can only be performed if domain-specific, world knowledge is available. For example, consider the processing of the word \"sales = in (7), (8) and (9). 7What is the average mark up for sales of stereo equipment? (8) What is the average mark down for sales of stereo equipment? (9) What is the average mark up during sales of stereo equipment? (10) What is the average mark down durlng sales of stereo equipment?", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "These four requests, which are so nelrly identical both lexically and syntactically, have very distinct meanings that derive from the fact that the correct sense of 'sliest in (7) ls quits different from the sense of \"sales = intended in (8), (9), end (10).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Nest people have little difficulty determining which sense of =sales = is intended in these sentences, and neither would a knowledge-based understander. The key to the disambiguation process involves world knowledge regarding retail sales.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Problems of anaphora pose similar problems. For example, suppose the following requests were submitted to a personnel data base:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "(11) List all salesmen with retirement plans along with their salaries.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "(12) List all offices with women managers along with their salaries.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "While these requests are syntactically identical, the referents for \"their\" in (11) end (12) occupy different syntactic positions. As human information processors, ve have no trouble understanding that salarie~ are associated with people, so retirement pllns and offices are never considered as possible referents.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Again, domain-specific world knouledge is helpful in understanding these requests.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "~Ug~u~al knQwlldgm i= m =uh=~i~u~m fo~ GQO\u00a2ID~ual knowlsdgg, One of inner|aliens to eaerge from the construction of domain-independent systems is t clever mechanism that extracts dosain-speclflc knowledge free the structure of the data base. For example, the resolution of the pronoun 'their = in both (11) and (12) above could be accomplished by using only structural (rather than conceptual) knowledge of the domain.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "For example, suppose the payroll database for (11) were structured such that SALARY and RETIRENENT-PLANS were fields within a SALESMAN file.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "It would then be possible to infer that ltheir= refers to =salesmen = in (11) by noting that SALARY is a field in the SALESMEN file, but that SALARY is not an entry in I RETIREMENT-PLANS file.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Unfortunately, this approach has lilited utility because it relies on a fortuitous de,abase structure.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Consider what would happen if the data base had a top-level ERPLOYEES file (rather than individual files for each type of employee) with fields for JOB-TYPE, SALARY, COMMISSIONS, and RE-TZRENENT-PLANS, With this database organization, it would not he possible to detersine that (13) List all salesmen who have secrebaries along with their comsissions. ltheir= refers ~o meal=amen\" and not \"secretaries = in (13) on the basis of the structure of the databass. To the naive user, however, the seining of this sentence is perfectly clear. A person who couldn't determine the referent of \"their = in (13) would not be perceived as having an adequate cossand of the English language and the same would be true for a computer system that did not understand the request.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "~i~fall= a==g~il~Id wi~b ~bm dQ\u00aezin:indag~ndln~ i~-In a knowledge-based systes such as PEARL, = natural language request is parsed into a conceptual representation of the meaning of the request. The retrieval routine is then generated free this concepbual representation. As a result, the parser is independent of the logical structure of the database. That is, the same parser can be used for databases with different logical structures, but the same information content.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Further, the same parser can be used whether the required information is located in = single file or in lultiple files.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "In a domaln-independent systes, the parser is entirely dependent on the structure of the database for domain-specific knowledge. As a result, one must restructure the parser for databases with identical content but different logical structure. Sisilarly, the output of the parser lust be very dlfferent vhen the required information Is contained in mulSiple files rather than a single file.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Because of their lack of conceptual knowledge regarding the database, domain-independent systems rely heavily on key words or phrases to indicate which database field iS being referred to. For example, 14Vhat is Bill Smith's ~ob &male?", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "High& be easily processed by simply retrieving the con&ants of a JOB-TITLE field.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Different vlys of referring ~o job title can also be handled as synonyms.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "However, dosiin\u00b0independent systems get into deep trouble vhen the database field that needs to be accessed is not directly indicated by key words or phrases in the input request. contains no key word or phrase to indicate that the CHILD-OF-AN-ALURNUS field should be accessed, In a knowledge-based system, the retrieval routine is generated from a conceptual representation of the meaning of the user query and therefore key words or phrases arm not required. A related problem occurs with queries involving a~reption or quantity.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "For example,", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "How many employees are in the sales department?", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "light require retrieving the value of a particular field (e.g. NUHBER-OF-EHPLOYEES), or it sight require totalling the number of records in the EH-PLOYEE file that have the correct DEPARTNENT field value, or, if the departments are broken down into offices, it light require totalling the NUN-BER-OF-ENPLOYEES field for each office.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "In m domain-independent system, the correct parse depends upon the structure of the database and is therefore difficult to handle in a general way. In a knowledge-based system such as PEARL, the different database structures would simply require altering the mapping between the conceptual representaSion of the parse and the retrieval query.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "Finally, this reliance on database structure can lead to wrong answers. A classic example is Harris' (1979) 'snowmobile problem =. Yhen Harris' ROBOT system interfaces with a file containing information about homeowner's insurance, the word 'snowmobile\" is defined as any number \u2022 0 in the 'snowmobile field\" of an insurance policy record. This means that as far as ROBOT is concerned, the question 'How many snowmobiles are there? = is no different from \"How many policies have snowmobile coverage?\" However, the correct answers to the two questions will often be very different.", |
| "cite_spans": [ |
| { |
| "start": 93, |
| "end": 107, |
| "text": "Harris' (1979)", |
| "ref_id": "BIBREF1" |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "If the first question is asked and the second question is answered, the result is an incorrect answer. If the first question cannot be answered due to the structure of the database, the system should inform the user the5 this is the case.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "I have argued above that conceptually-based domain-specific knowledge is absolutely essential for n|turll language database access systems. Systems that rely on dltabase structure for this domain-specific knowledge viii not achieve an acceptable level of performance --i.e. operate at the level of understanding of a programmer-technician.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "~oogluaioo=.", |
| "sec_num": null |
| }, |
| { |
| "text": "Because of the requirement for delian-specific knowledge, conceptually-based systems are restricted t~o limited domains and are not readily portable ~o new content areas.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "~oogluaioo=.", |
| "sec_num": null |
| }, |
| { |
| "text": "However, eliminating the domain-speciflc conceptual knowledge is throwing &he baby out with the ba&h water. The conceptually-based domain-specific knowledge is the key to robust understanding.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "~oogluaioo=.", |
| "sec_num": null |
| }, |
| { |
| "text": "The approach of the PEARL project with regard t~ the &ransportability problem is t~ try and Identify areas of discourse that are common t~ most domains and to build robust modules for natural language analysis within these domains.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "~oogluaioo=.", |
| "sec_num": null |
| }, |
| { |
| "text": "Examples of such domains are temporal reference, loci&ion reference, and report generation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "~oogluaioo=.", |
| "sec_num": null |
| }, |
| { |
| "text": "These modules are knowledge-based and can be used by a wide variety of domains to help extract ~hm conceptual content of a requss5.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "~oogluaioo=.", |
| "sec_num": null |
| } |
| ], |
| "back_matter": [], |
| "bib_entries": { |
| "BIBREF0": { |
| "ref_id": "b0", |
| "title": "~n:~9~h Und~\u00a3~aodiag~ ~ Cos-pu~nt HQdnl of In~ng\u00a3a~nd 8to,oaring fg\u00a3 Na~i-~[X \u00a7 Cg~D\u00a3ObgU~igO", |
| "authors": [ |
| { |
| "first": "N", |
| "middle": [], |
| "last": "Dyer", |
| "suffix": "" |
| } |
| ], |
| "year": 1982, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Dyer, N. (1982). ~n:~9~h Und~\u00a3~aodiag~ ~ Cos- pu~nt HQdnl of In~ng\u00a3a~nd 8to,oaring fg\u00a3 Na~i- ~[X \u00a7 Cg~D\u00a3ObgU~igO. Yale University, Computer Science Dept., Research Report #219.", |
| "links": null |
| }, |
| "BIBREF1": { |
| "ref_id": "b1", |
| "title": "Experience with ROBOT in 12 commercial natural language data base query applications, g\u00a3~oeding= Of ~b| O~b", |
| "authors": [ |
| { |
| "first": "T", |
| "middle": [ |
| "R" |
| ], |
| "last": "Harris", |
| "suffix": "" |
| } |
| ], |
| "year": 1979, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Harris, t. R. (1979). Experience with ROBOT in 12 commercial natural language data base query ap- plications, g\u00a3~oeding= Of ~b| O~b [o~ncna~ioo- al Joins Cgnfntnnco on &\u00a3~ificial [n~olllgonco.", |
| "links": null |
| }, |
| "BIBREF2": { |
| "ref_id": "b2", |
| "title": "LIFER: A natural language interface facility. SRZ Tech. Note 135", |
| "authors": [ |
| { |
| "first": "G", |
| "middle": [ |
| "G" |
| ], |
| "last": "Hendrix", |
| "suffix": "" |
| } |
| ], |
| "year": 1976, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Hendrix, G. G. (1976). LIFER: A natural language interface facility. SRZ Tech. Note 135. Dec.", |
| "links": null |
| }, |
| "BIBREF3": { |
| "ref_id": "b3", |
| "title": "Ibo 8~o~o~ of Ggo~ioo 8O-sHO\u00a3iOg", |
| "authors": [ |
| { |
| "first": "W", |
| "middle": [], |
| "last": "Lehnert", |
| "suffix": "" |
| } |
| ], |
| "year": 1978, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Lehnert, W. (1978). Ibo 8~o~o~ of Ggo~ioo 8O- sHO\u00a3iOg.", |
| "links": null |
| }, |
| "BIBREF4": { |
| "ref_id": "b4", |
| "title": "Nabural Language Data Base Access with Pearl", |
| "authors": [], |
| "year": null, |
| "venue": "EzoCmodlogs of ~be Hin~b Io~ntna~ional Conference on Comp~aSioQal Linguistic=", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Nabural Language Data Base Access with Pearl. EzoCmod- logs of ~be Hin~b Io~ntna~ional Conference on Comp~aSioQal Linguistic=, Prague, Czechoslo- vakia.", |
| "links": null |
| }, |
| "BIBREF5": { |
| "ref_id": "b5", |
| "title": "A LADOER user's guide. Technical Note 163", |
| "authors": [ |
| { |
| "first": "E", |
| "middle": [ |
| "D" |
| ], |
| "last": "5acerdoti", |
| "suffix": "" |
| }, |
| { |
| "first": "R", |
| "middle": [ |
| "C" |
| ], |
| "last": "Schank", |
| "suffix": "" |
| }, |
| { |
| "first": "R", |
| "middle": [], |
| "last": "Kbelson", |
| "suffix": "" |
| } |
| ], |
| "year": 1977, |
| "venue": "SRI Project", |
| "volume": "6891", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "5acerdoti, E. D. (1978). A LADOER user's guide. Technical Note 163. SRI Project 6891, Schank, R. C. and kbelson, R. (1977). ~\u00a3ig~.", |
| "links": null |
| }, |
| "BIBREF6": { |
| "ref_id": "b6", |
| "title": "PEARL: 'k Natural Language Analysis System for Information Retrieval", |
| "authors": [ |
| { |
| "first": "S", |
| "middle": [], |
| "last": "Shwartz", |
| "suffix": "" |
| } |
| ], |
| "year": 1977, |
| "venue": "G~IIs add U0da\u00a3s~anding", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Elm0=, G~IIs add U0da\u00a3s~anding, Lawrence Erl- baum Associates, Hillsdale Ne~ Jersey, 1977. Shwartz, S. (1982). PEARL: 'k Natural Language Analysis System for Information Retrieval (sub- mitted to AAAI-82/applications division).", |
| "links": null |
| }, |
| "BIBREF7": { |
| "ref_id": "b7", |
| "title": "The planes system: natural language access to a lar~e data base", |
| "authors": [ |
| { |
| "first": "D", |
| "middle": [ |
| "L" |
| ], |
| "last": "Waltz", |
| "suffix": "" |
| }, |
| { |
| "first": "", |
| "middle": [ |
| "T" |
| ], |
| "last": "Finin", |
| "suffix": "" |
| }, |
| { |
| "first": "F", |
| "middle": [], |
| "last": "Green", |
| "suffix": "" |
| }, |
| { |
| "first": "F", |
| "middle": [], |
| "last": "Conrad", |
| "suffix": "" |
| }, |
| { |
| "first": "B", |
| "middle": [], |
| "last": "Goodman", |
| "suffix": "" |
| }, |
| { |
| "first": "G", |
| "middle": [], |
| "last": "Hadden", |
| "suffix": "" |
| } |
| ], |
| "year": 1976, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Waltz, D. L., Finin. T., Green, F., Conrad, F., Goodman, B., Hadden, G. (1976). The planes system: natural language access to a lar~e data base. Coordinated Science Lab., Univ, of Il- linois, Urbane, Tech. Report T-34, (July 1976).", |
| "links": null |
| } |
| }, |
| "ref_entries": { |
| "FIGREF0": { |
| "type_str": "figure", |
| "num": null, |
| "uris": null, |
| "text": "-AN-ALUMNUS field, but the query (16) Is one of John Jones' paren&s an alumnus?" |
| } |
| } |
| } |
| } |
