Richard Eckart de Castilho

``` Hi Richard, thanks for your reply. So as a quick workaround, enhancing the pipeline to ... createEngineDescription(BerkeleyParser.class, BerkeleyParser.PARAM_WRITE_POS, false), createEngineDescription(StanfordPosTagger.class), ... did the trick. Looking at the BerkeleyParser googlecode...

``` (No text was entered with this change) ``` Original issue reported on code.google.com by `richard.eckart` on 2014-07-28 21:46:26 - **Labels added**: Module-berkeleyparser, DKPro-GPL

Jenkins, can you test this please?

``` (No text was entered with this change) ``` Original issue reported on code.google.com by `richard.eckart` on 2013-06-25 10:55:03

This seems to be available as a Maven Artifact here: http://svn.code.sf.net/p/bionlp/code/repo

Is GPL vs ASL an issue for you? If you run a compatible POS tagger before the `CoreNlpNamedEntityRecognizer` (i.e. the `CoreNlpPosTagger`), then you can also get e.g. `ORDINAL` tags: ```...

``` JCas jcas = runTest("en", "John bought one hundred laptops ."); String[] ne = { "[ 0, 4]Person(PERSON) (John)", "[ 12, 15]NamedEntity(NUMBER) (one)", "[ 16, 23]NamedEntity(NUMBER) (hundred)" }; ``` Looks...

I have committed the extended test which combines the Pos Tagger and the NER from CoreNLP here: https://github.com/dkpro/dkpro-core/blob/4f8d74fdb003c90fdef8ccff7039a799ab471699/dkpro-core-corenlp-gpl/src/test/java/org/dkpro/core/corenlp/CoreNlpPosTaggerAndNamedEntityRecognizerTest.java Feel free to play around with it and test additional number types...

I'd probably simply use a string feature even for numeric/boolean values... IMHO having an "Object" attribute also isn't a great solution because it would also require type-casting. The equivalent to...

I wonder why time expressions, monetary expressions and so on are even considered as named entities / handled by the CoreNLP NER tools. They are not really entities... in particular...