Skip to content

distinguish optional from obligatory arguments in Collins-style marking #17

@jeisner

Description

@jeisner

[item from the old TO-DO file dated 2002-04-07]

Mike's argument marking doesn't capture optional vs. obligatory. For example, determiners are treated as non-arguments: thus there's no notion of repeated determiners being bad. But this is unlikely to hurt Mike [Collins], because [he uses a discriminative model and] repeated determiners don't show up in the text. That's why using a smoothed model to actually parse [rather than looking at generative probability] would be a fairer evaluation ... at least for the supervised case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions