;;; Hey, emacs(1), this is -*- Mode: TDL; Coding: utf-8; -*- got it? ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;; ;;; third transfer phase, ERG-specific accomodation: these rules map from the ;;; LOGON transfer-level representations into MRS `idiosyncrasies' in the ERG. ;;; in some case, the ERG may just be lagging behind in development, or the ;;; ERG developers opt to maintain their design independent of LOGON (which we ;;; could hardly criticize, given there is no LOGON budget line item for ERG ;;; adaptation :-). however, ideally, this file should be small ;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;; ;;; while there is no specific `colon copula' in the ERG, default on the more ;;; underspecified fragment run-on configuration. ;;; colon_copula_ef := monotonic_mtr & [ INPUT [ LTOP #h0, RELS < [ PRED prpstn_m_rel, LBL #h0, ARG0 #i1, MARG #h2 ], [ PRED _colon_v_id_rel, LBL #h3, ARG1 #i4, ARG2 #i5 ] >, HCONS < qeq & [ HARG #h2, LARG #h3 ]> ], OUTPUT [ RELS < [ PRED implicit_conj_rel, LBL #h0, ARG0 i, L-HNDL #h6, L-INDEX #i7, R-HNDL #h8, R-INDEX #i9 ], [ PRED prpstn_m_rel, LBL #h6, ARG0 #i7, MARG #h10, TPC u, PSV u ], [ PRED unknown_rel, LBL #h11, ARG0 #i7, ARG #i4 ], [ PRED prpstn_m_rel, LBL #h8, ARG0 #i9, MARG #h12, TPC u, PSV u ], [ PRED unknown_rel, LBL #h13, ARG0 #i9, ARG #i5 ] >, HCONS < qeq & [ HARG #h10, LARG #h11 ], qeq & [ HARG #h12, LARG #h13 ] > ] ]. ;;; ;;; subject-to-subject raising verbs in the ERG lack the message that (in the ;;; 2006 way of thinking about messages) should be there; dan actually prefers ;;; to not add further messages (while expecting to eliminate all messages in a ;;; little more than half a year), hence patch things up here. ;;; begin_ssr_ef := ssr_message_ditch_amtr & [ INPUT.RELS < [ PRED "_begin_v_1_rel" ], ... > ]. start_ssr_ef := ssr_message_ditch_amtr & [ INPUT.RELS < [ PRED "_start_v_1_rel" ], ... > ]. ;;; ;;; _fix_me_ ;;; classifier insertion for plural mass nouns, e.g. `*informations'; requires ;;; SEM-I for proper generalization. move into a type. --- something similar ;;; presumably should be done for bare singulars, though we might rather want ;;; to fix their quantifier to _not_ transfer to `_a_q' in the first place? ;;; (25-apr-04; oe) plural_mass_noun_1_ef := monotonic_mtr & [ INPUT.RELS < [ PRED "_equipment_n_1_rel", LBL #h0, ARG0 #x1 & [ NUM pl, MARK test ] ] >, OUTPUT [ RELS < [ PRED "_piece_n_of_rel", LBL #h0, ARG0 #x1, ARG1 #x2 ], [ PRED bare_div_q_rel, LBL h, ARG0 #x2, RSTR #h3, BODY h ], [ PRED "_equipment_n_1_rel", LBL #h4, ARG0 #x2 & [ PERS 3, NUM sg, GRIND -, MARK complete ] ] >, HCONS < qeq & [ HARG #h3, LARG #h4 ] > ] ]. ;;; ;;; actually, bondo-san reminds us of potential for `scope' ambiguities in, ;;; e.g. `two big pieces of furniture' vs. `two pieces of big furniture', where ;;; he hypothesizes a contrast with respect to the contextually salient set of ;;; furniture and the `extent' of the property. hence, try another variant of ;;; classifier insertion that preserves the original index; this one should in ;;; theory work better for examples that would otherwise require extraposition, ;;; e.g. `two pieces of equipment i rented'. ;;; ;;; _fix_me_ ;;; which, after two more minutes of thought, we realize creates all sorts of ;;; interesting opportunities: parts of the MRS might want to continue using ;;; the `original' (now embedded) index, e.g. various modifiers maybe including ;;; relative clauses, while others would need to grap the new `top' index, e.g. ;;; the embedding predicate. (29-jul-04; bondo-san & oe) ;;; #| plural_mass_noun_2_ef := monotonic_mtr & [ INPUT.RELS < [ PRED "_equipment_n_1_rel", LBL #h0, ARG0 #x1 & [ NUM pl ] ] >, OUTPUT [ RELS < [ PRED "_piece_n_of_rel", LBL #h4, ARG0 #x2 & [ NUM pl ], ARG1 #x1 ], [ PRED bare_div_q_rel, LBL h, ARG0 #x2, RSTR #h3, BODY h ], [ PRED "_equipment_n_1_rel", LBL #h0, ARG0 #x1 & [ PERS 3, NUM sg] ] >, HCONS < qeq & [ HARG #h3, LARG #h4 ] > ] ]. |# ;;; ;;; _fix_me_ ;;; alternatively, we could do classifier insertion here. (25-apr-04; oe) ;;; a_q+equipment_n_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED "_equipment_n_1_rel", LBL #h1, ARG0 #x2 ] >, HCONS < qeq & [ HARG #h3, LARG #h1 ] > ], INPUT.RELS < [ PRED _a_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] >, OUTPUT.RELS < [ PRED bare_div_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] > ]. a_q+weather_n_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED "_weather_n_1_rel", LBL #h1, ARG0 #x2 ] >, HCONS < qeq & [ HARG #h3, LARG #h1 ] > ], INPUT.RELS < [ PRED _a_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] >, OUTPUT.RELS < [ PRED bare_div_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] > ]. ;;; ;;; _fix_me_ ;;; in tur/85, `[gir] mulighet [til]' comes out with a `bare_div_q'; should we ;;; alternatively go to plural here, or maybe make some change in NorGram? ;;; (29-aug-04; oe) bare_div_q+possibility_n_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED "_possibility_n_of_rel", LBL #h1, ARG0 #x2 ] >, HCONS < qeq & [ HARG #h3, LARG #h1 ] > ], INPUT.RELS < [ PRED bare_div_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] >, OUTPUT.RELS < [ PRED _a_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] > ]. ;;; ;;; _fix_me_ ;;; there appears to be a growth industry of quantifier adjustments; turn this ;;; into a type, but also aim for better harmonization. (27-jul-04; oe) ;;; udef_q+named_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED named_rel, LBL #h1, ARG0 #x2 ] >, HCONS < qeq & [ HARG #h3, LARG #h1 ] > ], INPUT.RELS < [ PRED udef_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] >, FILTER.RELS < [ PRED compound_name_rel, ARG1 #x2 ] >, OUTPUT.RELS < [ PRED proper_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] > ]. ;;; ;;; _fix_me_ ;;; this is getting old ... tidy up those quantifiers! (15-jun-05; jtl & oe) ;;; def_explicit_q+generic_nom_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED generic_entity_rel, LBL #h1, ARG0 #x2 ] >, HCONS < qeq & [ HARG #h3, LARG #h1 ] > ], INPUT.RELS < [ PRED def_explicit_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] >, OUTPUT.RELS < [ PRED def_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] > ]. ;;; ;;; _fix_me_ ;;; the ERG treats (all) gerunds as mass nouns, it seem; hence we need to make ;;; sure there is a suitable quantifier. maybe the rule creating the ;;; nominalization should be more careful instead? (25-apr-04; oe) ;;; a_q+nominalize_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED nominalization_rel, LBL #h1, ARG0 #x2 ] >, HCONS < qeq & [ HARG #h3, LARG #h1 ] > ], INPUT.RELS < [ PRED _a_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] >, OUTPUT.RELS < [ PRED implicit_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] > ]. ;;; ;;; _fix_me_ ;;; in fact, `to arrive takes a couple of days' has a `udef_q', not sure where ;;; we saw `bare_div_q' in the past; try the supertype `implicit_q' by default. ;;; (26-jul-04; oe) ;;; ;;; --- yes, `snoring takes a couple of days' has the `bare_div_q'. not sure ;;; about the good intentions here. (16-aug-04; oe) ;;; bare_div_q+nominalize_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED nominalization_rel, LBL #h1, ARG0 #x2 ] >, HCONS < qeq & [ HARG #h3, LARG #h1 ] > ], INPUT.RELS < [ PRED bare_div_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] >, OUTPUT.RELS < [ PRED implicit_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] > ]. udef_q+nominalize_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED nominalization_rel, LBL #h1, ARG0 #x2 ] >, HCONS < qeq & [ HARG #h3, LARG #h1 ] > ], INPUT.RELS < [ PRED udef_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] >, OUTPUT.RELS < [ PRED implicit_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] > ]. ;;; ;;; a related case, though maybe less worrisome: patterns like `regntøy' --> ;;; `rainclothes' (a plurale tantum) may also need their quantifier adjusted. ;;; (30-jun-04; oe) a_q+plural_ef := monotonic_mtr & [ INPUT.RELS < [ PRED _a_q_rel, LBL #h4, ARG0 #x2 & [ NUM pl ], RSTR #h3, BODY #h5 ] >, OUTPUT.RELS < [ PRED bare_div_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] > ]. ;;; ;;; partitives, it seems, are definite by their very nature. ;;; bare_div_q+part_of_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED part_of_rel, LBL #h1, ARG0 #x2 ] >, HCONS < qeq & [ HARG #h3, LARG #h1 ] > ], INPUT.RELS < [ PRED bare_div_q_rel ] >, OUTPUT.RELS < +copy+ & [ PRED def_q_rel ] > ]. ;;; ;;; while the grammars differ on their analysis of month names, we also need to ;;; make sure that `mofy' entities get their proper quantifier. (9-apr-05; oe) ;;; a_q+mofy_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED mofy_rel, LBL #h1, ARG0 #x2 ] >, HCONS < qeq & [ HARG #h3, LARG #h1 ] > ], INPUT.RELS < [ PRED _a_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] >, OUTPUT.RELS < [ PRED proper_q_rel, LBL #h4, ARG0 #x2, RSTR #h3, BODY #h5 ] > ]. ;;; ;;; _fix_me_ ;;; it looks like the memo about `same' now being analyzed as comparative did ;;; not quite make it to oslo; i am my skeptical self for now. and what about ;;; `other', `different', et al. then? (30-apr-05; oe) ;;; same_comp_ef := monotonic_mtr & [ CONTEXT.RELS < [ PRED "_same_a_as_rel", LBL #h0, ARG0 #e1, ARG1 #x2 ] >, FILTER.RELS < [ PRED comp_equal_rel, LBL #h0, ARG0 #e4, ARG1 #e1 ] >, OUTPUT.RELS < [ PRED comp_equal_rel, LBL #h0, ARG0 #e4, ARG1 #e1 ] > ]. ;;; ;;; insert `zero' complements for obligatory roles that were not supplied, so ;;; that we can generate at least. (30-jun-04; oe) ;;; carry_v_ef := monotonic_mtr & [ INPUT.RELS < [ PRED "_carry_v_1_rel", LBL #h0, ARG0 #e1, ARG1 #x2, ARG2 a ] >, OUTPUT [ RELS < [ PRED "_carry_v_1_rel", LBL #h0, ARG0 #e1, ARG1 #x2, ARG2 #x3 & x & [ PERS 3, NUM sg ] ], [ PRED _some_q_rel, ARG0 #x3, RSTR #h4 ], [ PRED thing_rel, LBL #h5, ARG0 #x3 ] >, HCONS < qeq & [ HARG #h4, LARG #h5 ] > ] ]. get_v_state_ef := monotonic_mtr & [ INPUT.RELS < [ PRED "_get_v_state_rel", LBL #h0, ARG0 #e1, ARG1 #x2, ARG2 a ] >, OUTPUT [ RELS < [ PRED "_get_v_state_rel", LBL #h0, ARG0 #e1, ARG1 #x2, ARG2 #h3 ], [ PRED prpstn_m_rel, LBL #h3, MARG #h4 ], [ PRED unspec_loc_rel, LBL #h5, ARG0 e_untensed, ARG1 #x2, ARG2 #x6 ], [ PRED def_q_rel, ARG0 #x6, RSTR #h7 ], [ PRED _there_a_1_rel, LBL #h8, ARG0 i, ARG1 #x6 ], [ PRED place_n_rel, LBL #h8, ARG0 #x6 ] >, HCONS < qeq & [ HARG #h4, LARG #h5 ], qeq & [ HARG #h7, LARG #h8 ] > ] ]. open_a_ef := monotonic_mtr & [ INPUT.RELS < [ PRED "_open_a_1_rel", LBL #h0, ARG0 #e1, ARG1 a ] >, OUTPUT [ RELS < [ PRED "_open_a_1_rel", LBL #h0, ARG0 #e1, ARG1 #x2 ], [ PRED pronoun_q_rel, ARG0 #x2, RSTR #h3 ], [ PRED pron_rel, LBL #h4, ARG0 #x2 & [ PERS 3, NUM pl ] ] >, HCONS < qeq & [ HARG #h3, LARG #h4 ] > ] ]. ;;; ;;; the (latest, maybe) ERG blocks some spurious ambiguity involving the there ;;; copula, e.g. in `there's a chair in my office', the ARG1 of `_in_p' cannot ;;; be the event of existence. (2-may-05; dan & oe) ;;; ;;; _fix_me_ ;;; dan suggested the HCONS condition in the CONTEXT to make sure we match the ;;; nominal EP rather than its quantifier; go through other rules, searching ;;; for regular expressions containing `_n_' and refine as needed. ;;; (2-may-05; oe) be_v_there_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED _be_v_there_rel, LBL #h, ARG0 #e0, ARG1 #x2 ], [ LBL #h42, ARG0 #x2 & x ] > , HCONS < qeq & [ LARG #h42 ] > ], INPUT.RELS < [ PRED #pred, LBL #h, ARG0 #e3, ARG1 #e0, ARG2 #x4 ] >, OUTPUT.RELS < [ PRED #pred, LBL #h42, ARG0 #e3, ARG1 #x2, ARG2 #x4 ] >, FLAGS.EQUAL < #x2 > ]. ;;; ;;; _fix_me_ ;;; `kim saw that sandy arrived' only has an analysis with the `understand' ;;; sense of `see'; generate PR for dan. (19-nov-04; oe) ;;; see+that_ef := monotonic_mtr & [ INPUT.RELS < [ PRED "_see_v_1_rel", LBL #h0, ARG0 #e1, ARG1 #x2, ARG2 #h3 & h ] >, OUTPUT.RELS < [ PRED "_see_v_understand_rel", LBL #h0, ARG0 #e1, ARG1 #x2, ARG2 #h3 & h ] >, FLAGS.EQUAL < #h3 > ]. ;;; ;;; _fix_me_ ;;; proper names: dan, apparently, has in some cases attempted to normalize ;;; CARG values, e.g. `Botnemarka' has [ CARG "botnemark" ]. (30-jun-04; oe) ;;; botnemarka_ef := noun_mtr & [ INPUT.RELS < [ PRED named_rel, CARG "botnemarka" ] >, OUTPUT.RELS < [ PRED named_rel, CARG "botnemark" ] > ]. oslofjorden_ef := noun_mtr & [ INPUT.RELS < [ PRED named_rel, CARG "oslofjorden" ] >, OUTPUT.RELS < [ PRED named_rel, CARG "oslofjord" ] > ]. ytre+standal_ef := noun_mtr & [ INPUT.RELS < [ PRED named_rel, CARG "ytre standal" ] >, OUTPUT.RELS < [ PRED named_rel, CARG "ytre_standal" ] > ]. ;;; ;;; to block `Vosses Utferdslag and Bergens Turlag', assume proper names are ;;; singular, unless the Andies Mountains tell us otherwise. ;;; named_sg_ef := monotonic_mtr & [ INPUT.RELS < [ PRED named_rel, LBL #h1, ARG0 #x2 & [ NUM no_number ], CARG #carg ] >, OUTPUT.RELS < [ PRED named_rel, LBL #h1, ARG0 #x2 & [ NUM sg ], CARG #carg ] > ]. ;;; ;;; number individuals, for now at least, are plural in the ERG. ;;; card_pl_ef := monotonic_mtr & [ INPUT.RELS < [ PRED card_rel, ARG0 #x & x & [ NUM sg ], ARG1 a, CARG "~[02-9][0-9]*" ] >, OUTPUT.RELS < +copy+ & [ ARG0 [ NUM pl ] ] >, FLAGS.EQUAL < #x > ]. ;;; ;;; _fix_me_ ;;; assuming that `_of_p' as a modifier on nouns always indicates possession ;;; (or at least is compatible with that interpretation :-), the following does ;;; allow generating `of' pseudo-possessives, though it would seem nicer maybe ;;; to not have to swap around roles and just underspecify generator input? ;;; (16-nov-04; oe & jtl) ;;; ;;; --- make sure this is done prior to the decision on pronoun reflexivity, so ;;; we get `the dog of himself' vs. `his dog'. (19-nov-04; oe) ;;; ;;; --- for the 28-apr-05 version of the ERG, this has been greatly improved, ;;; but for right now we still need a selected-for modifier relation. ;;; (28-apr-05; oe) ;;; --- the rule below, rightly, cycles; fortunately, we are now moving to the ;;; 29-apr-05 version of the grammar, eliminating the need for the selected-for ;;; prepositional EP. at the cost of swapping around its arguments: negotiate ;;; with helge. (29-apr-05; oe) ;;; poss_ef := monotonic_mtr & [ INPUT.RELS < [ PRED poss_rel, LBL #h0, ARG0 [ MARK test ], ARG1 #x1, ARG2 #x2 ] >, OUTPUT.RELS < [ PRED poss_rel, LBL #h0, ARG0 [ MARK complete ], ARG1 #x2, ARG2 #x1 ] > ]. reflexive_pronoun_ef := monotonic_mtr & [ INPUT.RELS < [ PRED pron_rel, LBL #h0, ARG0 #x1 ], [ PRED identity_rel, LBL #h0, ARG1 #x1 ] >, FILTER.RELS < [ PRED poss_rel, ARG2 #x1 ] >, OUTPUT.RELS < +copy+ & [ ARG0 [ PRONTYPE refl ] ] > ]. identity_ditch_ef := elision_mtr & [ INPUT.RELS < [ PRED identity_rel ] > ]. ;;; ;;; for transfer-internal purposes, we fake some abstractions over modalities; ;;; until the ERG makes these available in its semantic hierarchy, unfold the ;;; underspecification back into grammar-specific terms. (11-nov-04; oe) ;;; ;;; _fix_me_ ;;; this fails to work for conjoined arguments within the modal operator, e.g. ;;; `kim can sing and dance', where the embedded ARG1 is not directly accesible ;;; --- to get this to work, we would have to walk down a tree of conjoined ;;; events, or the ERG would have to decorate conjunct EPs (in VP coordination) ;;; with an ARG1 directly. (9-may-05; dan & oe) ;;; can_able+to_ef := monotonic_omtr & [ CONTEXT [ RELS < [ PRED "~_v_([^_]_)?rel$", LBL #h0, ARG0 #e42 & [ TENSE untensed ], ARG1 #x1 & x ] >, HCONS < qeq & [ HARG #h2, LARG #h0 ] > ], INPUT.RELS < [ PRED _can_v_modal_rel, LBL #h3, ARG0 #e4, ARG1 #h2 ] >, OUTPUT.RELS < [ PRED "_able_a_1_rel", LBL #h3, ARG0 #e4, ARG1 #x1, ARG2 #h5 ], [ PRED prpstn_m_rel, LBL #h5, MARG #h2 ] >, FLAGS.EQUAL < #x1, #e42 > ]. ;;; ;;; for clause-initial scopal adverbs, the ERG produces a semantics different ;;; from the VP-attached structure, e.g. `probably kim snores', has a total of ;;; two messages with the `probably' above the outermost message, while `kim ;;; probably sleeps' has only one message. dan has at times agreed that this ;;; is a spurious difference in semantics, while i conceded that for a large ;;; number of scopal adverbs the VP attachment will work fine. however, a few ;;; adverbs at least are syntactically constrained to not attach to VP, hence ;;; we need to manufacture the unwanted semantics in order to generate. ;;; (26-feb-06; oe) besides_a_ef := monotonic_mtr & [ CONTEXT [ RELS < [ PRED message_m_rel, ARG0 #e3, MARG #h4, TPC #u5, PSV #u6 ] >, HCONS < qeq & [ HARG #h4, LARG #h0 ] > ], INPUT.RELS < [ PRED "_besides_a_1_rel", LBL #h0, ARG0 #e1, ARG1 #h2 & h ] >, FILTER.RELS < [ PRED prpstn_m_rel, LBL #h2 ] >, OUTPUT.RELS < [ PRED "_besides_a_1_rel", LBL #h0, ARG0 #e1, ARG1 #h7 ], [ PRED prpstn_m_rel, LBL #h7, ARG0 #e3, MARG #h2, TPC #u5, PSV #u6 ] >, FLAGS.EQUAL < #h2 > ]. ;;; ;;; as of late, the ERG deliberately avoids activating intransitive versions of ;;; prepositions when there is an [ ARG2 u ] in the input. probably we will ;;; need to re-visit our notions of optionality and what it means for a role to ;;; be filled by an `unbound' variable. for now, just ditch those ARG2s. ;;; (6-jun-06; jtl & oe) intransitive_preposition_ef := monotonic_mtr & [ INPUT.RELS < [ PRED "~_p_", ARG2 #u & u & [ DITCH - ] ] >, OUTPUT.RELS < +copy+ & [ ARG2 [ DITCH + ] ] >, FLAGS.EQUAL < #u > ]. ;;; ;;; _fix_me_ ;;; NorGram (reasonably, i think) uses the abstract `unspec_loc' in sentences ;;; like `Hytta ligger i Oppland, 950 m o.h.'; for select internal arguments, ;;; at least, change that into an overt preposition, so that we can generate. ;;; (8-jun-06; oe) ;;; unspec_loc_meter_ef := monotonic_mtr & [ CONTEXT.RELS < [ PRED "_meter_n_1_rel",ARG0 #x0 ] >, INPUT.RELS < [ PRED unspec_loc_rel, ARG2 #x0 ] >, OUTPUT.RELS < +copy+ & [ PRED _at_p_rel ] > ]. ;;; ;;; _fix_me_ ;;; moving to the apr-05 version of the ERG, `bare_div_q' has been conflated ;;; with `udef_q', so (for right now), accomodate that post-transfer. ;;; (20-apr-05; dan & oe) bare_div_q_ef := monotonic_mtr & [ INPUT.RELS < [ PRED bare_div_q_rel ] >, OUTPUT.RELS < +copy+ & [ PRED udef_q_rel ] > ]. missing_quantifier_sg_ef := monotonic_mtr & [ CONTEXT.RELS < [ PRED "~_n_", LBL #h1, ARG0 #x2 & x & [ NUM sg ] ] >, FILTER.RELS < [ ARG0 #x2, RSTR #h3 & h ] >, OUTPUT [ RELS < [ PRED some_q_rel, ARG0 #x2, RSTR #h4 ] >, HCONS < qeq & [ HARG #h4, LARG #h1 ] > ], FLAGS.EQUAL < #x2, #h3 > ]. missing_quantifier_pl_ef := monotonic_mtr & [ CONTEXT.RELS < [ PRED "~_n_", LBL #h1, ARG0 #x2 & x & [ NUM pl ] ] >, FILTER.RELS < [ ARG0 #x2, RSTR #h3 & h ] >, OUTPUT [ RELS < [ PRED udef_q_rel, ARG0 #x2, RSTR #h4 ] >, HCONS < qeq & [ HARG #h4, LARG #h1 ] > ], FLAGS.EQUAL < #x2, #h3 > ].