| tech,4-1-P85-1019,ak | languages </term> . We have implemented a <term> | restricted domain parser | </term> called <term> Plume </term> . Building | #15828 We have implemented arestricted domain parser called Plume. | |
| tool,8-1-P85-1019,ak | restricted domain parser </term> called <term> | Plume | </term> . Building on previous work at Carnegie-Mellon | #15832 We have implemented a restricted domain parser calledPlume. | |
| tool,16-2-P85-1019,ak | Carnegie-Mellon University e.g. [ 4 , 5 , 8 ] , <term> | Plume 's | </term> approach to <term> parsing </term> is | #15850 Building on previous work at Carnegie-Mellon University e.g. [4, 5, 8],Plume 's approach to parsing is based on semantic caseframe instantiation. | |
| tech,20-2-P85-1019,ak | , <term> Plume 's </term> approach to <term> | parsing | </term> is based on <term> semantic caseframe | #15854 Building on previous work at Carnegie-Mellon University e.g. [4, 5, 8], Plume's approach toparsing is based on semantic caseframe instantiation. | |
| tech,24-2-P85-1019,ak | to <term> parsing </term> is based on <term> | semantic caseframe instantiation | </term> . This has the advantages of <term> | #15858 Building on previous work at Carnegie-Mellon University e.g. [4, 5, 8], Plume's approach to parsing is based onsemantic caseframe instantiation. | |
| other,5-3-P85-1019,ak | </term> . This has the advantages of <term> | efficiency | </term> on <term> grammatical input </term> , | #15867 This has the advantages ofefficiency on grammatical input, and robustness in the face of ungrammatical input. | |
| other,7-3-P85-1019,ak | advantages of <term> efficiency </term> on <term> | grammatical input | </term> , and <term> robustness </term> in the | #15869 This has the advantages of efficiency ongrammatical input, and robustness in the face of ungrammatical input. | |
| other,11-3-P85-1019,ak | <term> grammatical input </term> , and <term> | robustness | </term> in the face of <term> ungrammatical | #15873 This has the advantages of efficiency on grammatical input, androbustness in the face of ungrammatical input. | |
| other,16-3-P85-1019,ak | <term> robustness </term> in the face of <term> | ungrammatical input | </term> . While <term> Plume </term> is well | #15878 This has the advantages of efficiency on grammatical input, and robustness in the face ofungrammatical input. | |
| tool,1-4-P85-1019,ak | <term> ungrammatical input </term> . While <term> | Plume | </term> is well adapted to simple <term> declarative | #15882 WhilePlume is well adapted to simple declarative and imperative utterances, it handles passives, relative clauses and interrogatives in an ad hoc manner leading to patchy syntactic coverage. | |
| other,7-4-P85-1019,ak | Plume </term> is well adapted to simple <term> | declarative and imperative utterances | </term> , it handles <term> passives </term> | #15888 While Plume is well adapted to simpledeclarative and imperative utterances, it handles passives, relative clauses and interrogatives in an ad hoc manner leading to patchy syntactic coverage. | |
| other,14-4-P85-1019,ak | imperative utterances </term> , it handles <term> | passives | </term> , <term> relative clauses </term> and | #15895 While Plume is well adapted to simple declarative and imperative utterances, it handlespassives, relative clauses and interrogatives in an ad hoc manner leading to patchy syntactic coverage. | |
| other,16-4-P85-1019,ak | , it handles <term> passives </term> , <term> | relative clauses | </term> and <term> interrogatives </term> in | #15897 While Plume is well adapted to simple declarative and imperative utterances, it handles passives,relative clauses and interrogatives in an ad hoc manner leading to patchy syntactic coverage. | |
| other,19-4-P85-1019,ak | </term> , <term> relative clauses </term> and <term> | interrogatives | </term> in an ad hoc manner leading to patchy | #15900 While Plume is well adapted to simple declarative and imperative utterances, it handles passives, relative clauses andinterrogatives in an ad hoc manner leading to patchy syntactic coverage. | |
| other,28-4-P85-1019,ak | an ad hoc manner leading to patchy <term> | syntactic coverage | </term> . This paper outlines <term> Plume </term> | #15909 While Plume is well adapted to simple declarative and imperative utterances, it handles passives, relative clauses and interrogatives in an ad hoc manner leading to patchysyntactic coverage. | |
| tool,3-5-P85-1019,ak | coverage </term> . This paper outlines <term> | Plume | </term> as it currently exists and describes | #15915 This paper outlinesPlume as it currently exists and describes our detailed design for extending Plume to handle passives, relative clauses, and interrogatives in a general manner. | |
| tool,15-5-P85-1019,ak | our detailed design for extending <term> | Plume | </term> to handle <term> passives </term> , <term> | #15927 This paper outlines Plume as it currently exists and describes our detailed design for extendingPlume to handle passives, relative clauses, and interrogatives in a general manner. | |
| other,18-5-P85-1019,ak | extending <term> Plume </term> to handle <term> | passives | </term> , <term> relative clauses </term> , and | #15930 This paper outlines Plume as it currently exists and describes our detailed design for extending Plume to handlepassives, relative clauses, and interrogatives in a general manner. | |
| other,20-5-P85-1019,ak | </term> to handle <term> passives </term> , <term> | relative clauses | </term> , and <term> interrogatives </term> in | #15932 This paper outlines Plume as it currently exists and describes our detailed design for extending Plume to handle passives,relative clauses, and interrogatives in a general manner. | |
| other,24-5-P85-1019,ak | <term> relative clauses </term> , and <term> | interrogatives | </term> in a general manner . <term> Intersentential | #15936 This paper outlines Plume as it currently exists and describes our detailed design for extending Plume to handle passives, relative clauses, andinterrogatives in a general manner. |
