| lr,10-4-C88-2166,bq | explicit and implicit information from <term> | machine-readable dictionaries ( MRD 's ) | </term> to create a <term> broad coverage lexicon | #16002 We have drawn primarily on explicit and implicit information frommachine-readable dictionaries ( MRD 's ) to create a broad coverage lexicon. |
| lr,12-3-C88-2166,bq | and building <term> COMPLEX </term> , a <term> | computational lexicon | </term> designed to be a repository of <term> | #15970 This paper presents our experience in planning and building COMPLEX, acomputational lexicon designed to be a repository of shared lexical information for use by Natural Language Processing (NLP) systems. |
| lr,19-4-C88-2166,bq | dictionaries ( MRD 's ) </term> to create a <term> | broad coverage lexicon | </term> . For <term> intelligent interactive | #16011 We have drawn primarily on explicit and implicit information from machine-readable dictionaries (MRD's) to create abroad coverage lexicon. |
| lr,21-1-C88-2166,bq | and types of information into its <term> | lexicon | </term> according to its individual needs | #15936 Although every natural language system needs a computational lexicon, each system puts different amounts and types of information into itslexicon according to its individual needs. |
| lr,7-1-C88-2166,bq | natural language system </term> needs a <term> | computational lexicon | </term> , each <term> system </term> puts different | #15922 Although every natural language system needs acomputational lexicon, each system puts different amounts and types of information into its lexicon according to its individual needs. |
| lr-prod,9-3-C88-2166,bq | experience in planning and building <term> | COMPLEX | </term> , a <term> computational lexicon </term> | #15967 This paper presents our experience in planning and buildingCOMPLEX, a computational lexicon designed to be a repository of shared lexical information for use by Natural Language Processing (NLP) systems. |
| other,20-3-C88-2166,bq | </term> designed to be a repository of <term> | shared lexical information | </term> for use by <term> Natural Language | #15978 This paper presents our experience in planning and building COMPLEX, a computational lexicon designed to be a repository ofshared lexical information for use by Natural Language Processing (NLP) systems. |
| tech,11-1-C88-2166,bq | computational lexicon </term> , each <term> | system | </term> puts different amounts and types | #15926 Although every natural language system needs a computational lexicon, eachsystem puts different amounts and types of information into its lexicon according to its individual needs. |
| tech,2-1-C88-2166,bq | lexical gap </term> . Although every <term> | natural language system | </term> needs a <term> computational lexicon | #15917 Although everynatural language system needs a computational lexicon, each system puts different amounts and types of information into its lexicon according to its individual needs. |
| tech,26-3-C88-2166,bq | lexical information </term> for use by <term> | Natural Language Processing ( NLP ) systems | </term> . We have drawn primarily on explicit | #15984 This paper presents our experience in planning and building COMPLEX, a computational lexicon designed to be a repository of shared lexical information for use byNatural Language Processing ( NLP ) systems. |
| tech,8-2-C88-2166,bq | some of the information needed across <term> | systems | </term> is shared or identical information | #15951 However, some of the information needed acrosssystems is shared or identical information. |
