Forcing the stanford parser to accept POS tags not licensed by the parser's lexicon?

There is at present no way to make the parse tag things in a way that it regards as "too weird". If it regards a tag for a word as impossible, you can't make it possible, but you can specify what it should use within the range of what it regards as possible. Normally this is enough.It should be enough here.

Here's an example. As you note, it often gets imperatives wrong unaided (partly because they're not well-evidenced in the training data.It doesn't always get them wrong, but it commonly does, and I chose 3 that it does get wrong.

There is at present no way to make the parse tag things in a way that it regards as "too weird". If it regards a tag for a word as impossible, you can't make it possible, but you can specify what it should use within the range of what it regards as possible. Normally this is enough.It should be enough here.

Here's an example. As you note, it often gets imperatives wrong unaided (partly because they're not well-evidenced in the training data.It doesn't always get them wrong, but it commonly does, and I chose 3 that it does get wrong: $ cat imper. Txt Use care when opening.

Brush your hair! Shut the door. $ java -cp stanford-parser.

Jar edu.stanford.nlp.parser.lexparser. LexicalizedParser englishPCFG.ser. Gz imper.

Txt 2> /dev/null (ROOT (S (NP (NNP Use)) (VP (VBP care) (SBAR (WHADVP (WRB when)) (S (VP (VBG opening))))) (. .))) (ROOT (NP (NP (NNP Brush)) (NP (PRP$ your) (NN hair)) (.!))) (ROOT (NP (NP (NNP Shut)) (NP (DT the) (NN door)) (. . ))) But with tokenized and partly tagged text like this: $ cat imper. Tok Use_VB care when opening .

Brush_VB your hair! Shut_VB the door . All is fixed: $ java -cp stanford-parser.

Jar edu.stanford.nlp.parser.lexparser. LexicalizedParser -tokenized -tagSeparator _ englishPCFG.ser. Gz imper.

Tok 2> /dev/null (ROOT (S (VP (VB Use) (NP (NN care)) (SBAR (WHADVP (WRB when)) (S (VP (VBG opening))))) (. . ))) (ROOT (S (VP (VB Brush) (NP (PRP$ your) (NN hair))) (.!))) (ROOT (S (VP (VB Shut) (NP (DT the) (NN door))) (. . ))) But you do have to use the right tags.It won't tag "Using" as a VB.

That counts as too weird. "Using" as a verb should be a VBG.It's the present participle form, not the bare verb used in imperatives.

The following words (appearing in the base form as I have them below, as in "Number the lines from 1 to 10. " or "Delete all instances of "bar" following "foo. ") in my data are the most problematic imperative verbs for the parser: 'display, print, delete, sort, extract, split, number, count, convert, insert, align, center, substitute, change, reverse, join, swap, remove, undo, group, strip' With a few notable exceptions (number, delete, print), the words in this list are almost never accepted as verbs in my data.

– iltrn Jun 10 at 17:00.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.