We think that in any case, in order to get an analysis where creer and lo are one word, they must be one token at the level of YY-input (even if Freeling tokenizes them into two).
The wiki says:
Each token in the above example has the following format:
(id, start, end, [link,] path+, form [surface], ipos, lrule+[, {pos p}+])
It would appear that the correct YY-input might then be (scroll all the way to the right):
(1, 0, 1, <0:6>, 1, "costar" "cuesta", 0, "vmip3s0", "vmip3s0" 0.946188340807175) (2, 1, 2, <7:14>, 1, "creer" "creerlo", 0, "vmn0000" "+pp3cna00", "+pp3cna00" 1.0) (3, 2, 3, <14:15>, 1, "." ".", 0, "fp", "fp" 1.0)
Indeed I do get a parse, yay! Although I am not seeing the surface forms where I want them but I hope this is a minor issue:
Full ACE output:
(1, 0, 1, <0:6>, 1, "costar" "cuesta", 0, "vmip3s0", "vmip3s0" 0.946188340807175) (2, 1, 2, <7:14>, 1, "creer" "creerlo", 0, "vmn0000" "+pp3cna00", "+pp3cna00" 1.0) (3, 2, 3, <14:15>, 1, "." ".", 0, "fp", "fp" 1.0)
SENT: (yy mode)
[ LTOP: h0 INDEX: event2 [ event SORT: semsort E.TENSE: pres E.ASPECT: aspect E.MOOD: ind SF: prop ] RELS: < [ "_costar_v_rel"<-1:-1> LBL: handle1 [ handle SORT: semsort ] WLINK: list CFROM: *top* CTO: *top* ARG0: event2 ARG1: handle7 [ handle SORT: semsort ] ARG2: ref-ind8 [ ref-ind SORT: ani_bpart_hum_soc PNG.PN: pernum PNG.GEN: gender PRONTYPE: prontype DEF: bool DIVISIBLE: bool ] ] [ "_creer_v_rel"<-1:-1> LBL: handle3 [ handle SORT: semsort ] WLINK: list CFROM: *top* CTO: *top* ARG0: event12 [ event SORT: semsort E.TENSE: nontense E.ASPECT: no-aspect E.MOOD: mood SF: prop ] ARG1: ref-ind8 ARG2: ref-ind13 [ ref-ind SORT: semsort PNG.PN: 3sg PNG.GEN: masc PRONTYPE: prontype DEF: bool DIVISIBLE: bool ] ] > HCONS: < h0 qeq handle1 handle7 qeq handle3 > ] ; (1715 hd-sb_c -1.536990 0 3 (1710 hd_optcmp-v_c -0.119250 0 1 (1709 vmip3s0 0.000000 0 1 (1708 v_ppa*_sbj-vp-inf-oc_dlr 0.000000 0 1 (7 costar_v-pp_a-sbj_cp_p_sub 0.000000 0 1 ("costar" 1 "token [ +FORM \"costar\" +FROM \"0\" +TO \"6\" +ID diff-list [ LIST cons [ FIRST \"1\" REST list ] LAST list ] +POS pos [ +TAGS cons [ FIRST \"vmip3s0\" REST null ] +PRBS cons [ FIRST \"0.946188\" REST null ] ] +CLASS token_class +TRAIT token_trait +PRED predsort +CARG string ]"))))) (1714 hd-pt_c -1.417740 1 3 (1712 +PP3CNA00 -1.417740 1 2 (1711 vmn0000 -1.417740 1 2 (1693 v_acc_dlr 0.000000 1 2 (9 creer_v-np_rcp 0.000000 1 2 ("creer" 2 "token [ +FORM \"creer\" +FROM \"7\" +TO \"14\" +ID diff-list [ LIST cons [ FIRST \"2\" REST list ] LAST list ] +POS pos [ +TAGS cons [ FIRST \"+pp3cna00\" REST null ] +PRBS cons [ FIRST \"1.000000\" REST null ] ] +CLASS token_class +TRAIT token_trait +PRED predsort +CARG string ]"))))) (1713 fp 0.000000 2 3 (17 fstop_pt 0.000000 2 3 ("." 3 "token [ +FORM \".\" +FROM \"14\" +TO \"15\" +ID diff-list [ LIST cons [ FIRST \"3\" REST list ] LAST list ] +POS pos [ +TAGS cons [ FIRST \"fp\" REST null ] +PRBS cons [ FIRST \"1.000000\" REST null ] ] +CLASS token_class +TRAIT token_trait +PRED predsort +CARG string ]")))))
NOTE: 1 readings, added 1054 / 593 edges to chart (453 fully instantiated, 27 actives used, 235 passives used) RAM: 6281k
As usual, special thanks to @Dan who said yesterday in the GE meeting: “Surely it is documented somewhere how to write YY when you have more than one lexical rule”. It ended up so simple in the end!
