Comments on: Getting OpenNLP parser to work http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/ > From inner thoughts to the outer limits of Alexandre Rafalovitch Wed, 20 Aug 2008 18:58:28 +0000 http://wordpress.org/?v=2.6.1 By: Alexandre Rafalovitch http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-238 Alexandre Rafalovitch Wed, 28 May 2008 12:14:57 +0000 http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-238 Quek, I don't buy 'read the source' argument in the context of this article. Code, and especially NLP code, is not easy to read and therefore has a higher learning curve than tutorials and good documentations. Therefore, people with not enough time (or patience) will drop out early and go look at something else. That's why one of the measure of success for open source projects is whether they have a good introductory book published. Obviously, not everything can be documented, but it should be easy to at least start quickly and judge whether it is worth spending extra time on looking through the code. That's what happened with Stanford parser for me. There was just enough documentation to start and then I read the source to figure out <a href="http://blog.outerthoughts.com/2007/07/duplicating-tagseparator-effect-when-using-stanford-parser-programmatically/" rel="nofollow">the additional options</a>. Quek,

I don’t buy ‘read the source’ argument in the context of this article. Code, and especially NLP code, is not easy to read and therefore has a higher learning curve than tutorials and good documentations. Therefore, people with not enough time (or patience) will drop out early and go look at something else. That’s why one of the measure of success for open source projects is whether they have a good introductory book published.

Obviously, not everything can be documented, but it should be easy to at least start quickly and judge whether it is worth spending extra time on looking through the code.

That’s what happened with Stanford parser for me. There was just enough documentation to start and then I read the source to figure out the additional options.

]]> By: quek http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-237 quek Wed, 28 May 2008 03:52:50 +0000 http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-237 dude... daniel maclaren's tutorial is based on code within the OpenNLP package itself. In fact almost all the code's taken from the english.* java files. It is open source after all, all you have to do is read through the source. chill man chill. dude… daniel maclaren’s tutorial is based on code within the OpenNLP package itself. In fact almost all the code’s taken from the english.* java files. It is open source after all, all you have to do is read through the source. chill man chill.

]]> By: Karalabe http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-239 Karalabe Tue, 08 Apr 2008 19:41:44 +0000 http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-239 You can use 2 lines of code to get you're sentences parsed :) [figured it out partly thanks to the tutorial you linked in] <code> String sentence = "This is some random sentence to get you started"; // Load the serialized parser ParserME parser = TreebankParser.getParser("wherever-your-parser-dir-is/"); // Parse the sentence, and fetch an array containing the best 1 parses, access the first (0) element and display it TreebankParser.parseLine(sentence, parser, 1)[0].show(); </code> You can use 2 lines of code to get you’re sentences parsed :) [figured it out partly thanks to the tutorial you linked in]


String sentence = "This is some random sentence to get you started";

// Load the serialized parser
ParserME parser = TreebankParser.getParser("wherever-your-parser-dir-is/");

// Parse the sentence, and fetch an array containing the best 1 parses, access the first (0) element and display it
TreebankParser.parseLine(sentence, parser, 1)[0].show();

]]> By: Alexandre Rafalovitch http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-236 Alexandre Rafalovitch Sat, 16 Feb 2008 17:33:31 +0000 http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-236 Thank you Alyona, This looks interesting as well. Thank you Alyona,

This looks interesting as well.

]]> By: Alyona http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-235 Alyona Wed, 13 Feb 2008 21:58:01 +0000 http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-235 I found this tutorial useful: http://www.codeproject.com/KB/recipes/englishparsing.aspx I found this tutorial useful:
http://www.codeproject.com/KB/.....rsing.aspx

]]> By: Jeryl http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-234 Jeryl Tue, 11 Dec 2007 00:44:42 +0000 http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-234 worked for me, whats your email i can send u sample code(as eclipse project with junit tests.) worked for me, whats your email i can send u sample code(as eclipse project with junit tests.)

]]> By: Alexandre Rafalovitch http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-233 Alexandre Rafalovitch Sun, 12 Aug 2007 12:56:05 +0000 http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-233 Matthew, Same application as with the previous two parsers: trying to extract complex named entities out of long, non-trivial sentences. Matthew,

Same application as with the previous two parsers: trying to extract complex named entities out of long, non-trivial sentences.

]]> By: Matthew http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-232 Matthew Sun, 12 Aug 2007 11:36:23 +0000 http://blog.outerthoughts.com/2007/08/getting-opennlp-parser-to-work/#comment-232 Sounds fun. Any particular application in mind for this toolset? Sounds fun. Any particular application in mind for this toolset?

]]>