<div dir="ltr">Hi,<div><br></div><div>Thank you for your response! Is there anyway to prevent sentences like "_generic_vbd_ is a person." to be parseable where "_generic_vbd_" is being recognized as a "NN" POS generic? Would this require turning off the unknown word machinery and adding these generics as lexical entries?</div><div><br></div><div>I am interested because the grammaticality of my language model is important to me. Thanks! Please let me know!</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 12, 2018 at 2:10 PM, Stephan Oepen <span dir="ltr"><<a href="mailto:oe@ifi.uio.no" target="_blank">oe@ifi.uio.no</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi johnny,<br>
<br>
> [...] A sample from my language model might look like "generic_proper_ne had<br>
<span class="">> VBP_u_unknown a cat ." I want to see if these sequences can be parsed by the<br>
> ERG.<br>
<br>
</span>if you look at ‘gle.tdl’ in the ERG sources, it provides the<br>
definitions of the generic lexical entries that are put to use in<br>
unknown word handling. for debugging purposes (similar to what you<br>
have in mind, i think) they all have a unique orthography—which you<br>
should be able to just give to the parser; please see the attachment,<br>
for how this works on the ERG on-line interface.<br>
<br>
best wishes, oe<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Johnny Wei</div></div>
</div>