Hi! Thank you for your advise. I implemented some rules in the application and it looks fine. There is no need to complicate the chunker.
William On Fri, Aug 5, 2011 at 11:21 AM, Jason Baldridge <[email protected]>wrote: > It's not clear to me that head identification should be done as part of the > prediction unless it improves performance across a couple of languages. > With > things as small as chunks, I'm guessing regular expressions, or a secondary > head prediction model would do the trick. Any reasons to complicate the > chunker itself? > > Jason > > On Wed, Aug 3, 2011 at 8:38 AM, Jörn Kottmann <[email protected]> wrote: > > > On 8/3/11 3:24 PM, [email protected] wrote: > > > >> It would be available for other languages. Just need to add the mark to > >> the > >> corpus tags. I think it is much better to use the Chunker because it is > >> faster and adding the head (some people call it main). > >> > > > > I see, and that depends on training data which labels the head. Do you > know > > of any for other languages? > > > > Maybe we should have a dedicated head finder as part of the parser, which > > could also run stand-alone. > > > > Would be nice to know what Jason thinks. > > > > In the coref component we have several models which could also be > > interesting > > for some people to use without the other coref stuff, for example the > model > > to > > label the gender of an entity. > > > > Jörn > > > > > > -- > Jason Baldridge > Assistant Professor, Department of Linguistics > The University of Texas at Austin > http://www.jasonbaldridge.com > http://twitter.com/jasonbaldridge >
