-
Notifications
You must be signed in to change notification settings - Fork 3
Closed
Description
One analysis that LKB gives me:
The indexed MRS for this analysis:
<h1,e3:PROP:PRES:INDICATIVE:-:-,
{h4:_that_q_dem<0:4>(x7:3:SG:+, h6, h5),
h8:_car_n_1<5:8>(x7),
h2:ellipsis_ref(e3, x7),
h2:_in_p_state<12:14>(e9:PROP:UNTENSED:INDICATIVE:-:-, e3, x10:3:SG:+),
h11:_the_q<15:18>(x10, h13, h12),
h14:_wrong_a_with<19:24>(e15:PROP:UNTENSED:INDICATIVE:BOOL:-, x10),
h14:compound<25:37>(e17:PROP:UNTENSED:INDICATIVE:-:-, x10, x16:3:SG:-),
h18:udef_q<25:32>(x16, h19, h20),
h21:_traffic_n_1<25:32>(x16),
h14:_lane_n_1<33:37>(x10)},
{h1 qeq h2,h6 qeq h8,h13 qeq h14,h19 qeq h21}>
One scoped MRS
_that_q_dem(x7,
_car_n_1(x7),
_the_q(x10,
udef_q(x16,
_traffic_n_1(x16),
_wrong_a_with(e15, x10) /\ compound(e17, x10, x16) /\ _lane_n_1(x10)),
ellipsis_ref(e3, x7) /\ _in_p_state(e9, e3, x10)))
Does it make sense to have a compound split in two different labels (e.g. h21 and h14)? The udef_q quantifier restriction shouldn't be _traffic_n_1(x16) /\ compound(e17, x10, x16) /\ _lane_n_1(x10))?
Metadata
Metadata
Assignees
Labels
No labels
