Extracting all Nouns from a text file using nltk
Asked Answered
S

6

22

Is there a more efficient way of doing this? My code reads a text file and extracts all Nouns.

import nltk

File = open(fileName) #open file
lines = File.read() #read all lines
sentences = nltk.sent_tokenize(lines) #tokenize sentences
nouns = [] #empty to array to hold all nouns

for sentence in sentences:
     for word,pos in nltk.pos_tag(nltk.word_tokenize(str(sentence))):
         if (pos == 'NN' or pos == 'NNP' or pos == 'NNS' or pos == 'NNPS'):
             nouns.append(word)

How do I reduce the time complexity of this code? Is there a way to avoid using the nested for loops?

Thanks in advance!

Sawfish answered 7/11, 2015 at 20:54 Comment(1)
Replace the if condition with if pos.startswith('NN'): , also use a set or collections.Counter, don't keep a list. And do some map/reduce instead of a list comprehension. Otherwise, try shallow parsing, aka chunkingGiraldo
D
34

If you are open to options other than NLTK, check out TextBlob. It extracts all nouns and noun phrases easily:

>>> from textblob import TextBlob
>>> txt = """Natural language processing (NLP) is a field of computer science, artificial intelligence, and computational linguistics concerned with the inter
actions between computers and human (natural) languages."""
>>> blob = TextBlob(txt)
>>> print(blob.noun_phrases)
[u'natural language processing', 'nlp', u'computer science', u'artificial intelligence', u'computational linguistics']
Dinodinoflagellate answered 7/11, 2015 at 21:53 Comment(4)
You say "It extracts all nouns and noun phrases easily" but I don't see the option to extract nouns only. How could I get nouns alone in your example such as "computer" or "science"?Nunnery
you could use blob.tags to filter out NN only something like [n for n,t in blob.tags if t == 'NN'].Dinodinoflagellate
Personally, I have found that TextBlob doesn't perform nearly as well as nltkGlad
The code may be simpler, but textblob calls the NLTK to tokenize and tag. This cannot reduce the "time complexity" of the OP's code.Impatient
S
31
import nltk

lines = 'lines is some string of words'
# function to test if something is a noun
is_noun = lambda pos: pos[:2] == 'NN'
# do the nlp stuff
tokenized = nltk.word_tokenize(lines)
nouns = [word for (word, pos) in nltk.pos_tag(tokenized) if is_noun(pos)] 

print nouns
>>> ['lines', 'string', 'words']

Useful tip: it is often the case that list comprehensions are a faster method of building a list than adding elements to a list with the .insert() or append() method, within a 'for' loop.

Sisneros answered 7/11, 2015 at 21:18 Comment(5)
The answer is a correct train of thought. Using this is cleaner: is_noun = lambda pos: True if pos[:2] == 'NN'. Note: List comprehension is not necessary faster than for loop. It's just that you don't have to materialize a list and deal with nested loops as generators instead of list.Giraldo
@Giraldo - I didn't use something like ... pos[:2] == 'NN'..., because it might match undesirable strings. For all I know, there might be a pos that has a value of 'NNA', and we do not want to match that. Strictly speaking, the True if and else False parts aren't necessary either, but I included them for clarity. Good point about list comprehensions not being necessarily faster than a loop (I guess I was being glib there) - I've edited the post accordingly.Sisneros
Just out of curiosity, could you give an instance of 'NNA'? It's so that we can do some checks in NLTK on other things not related to this question though =) . Technically, there shouldn't be any tags outside of this tagset: ling.upenn.edu/courses/Fall_2003/ling001/penn_treebank_pos.htmlGiraldo
@Giraldo - The scenario I presented was hypothetical, and the point that I was making was that I didn't know, a priori, what values the 'pos' variable might take (maybe I should have said something like 'NNABCDEFG' instead of 'NNA' to make that notion clearer), so to be safe, I went with the conditional parameters that were presented in the original question. That conditional line, and any other part of the answer I provided can be modified as necessary; I suspect that the performance difference between the 'pos[:2]' variant, and the long conditional that I presented, is pretty marginal.Sisneros
@Giraldo - alright - I've edited the post to include your suggestion, to make the answer cleaner. Cheers ;)Sisneros
C
18

You can achieve good results using nltk, Textblob, SpaCy or any of the many other libraries out there. These libraries will all do the job but with different degrees of efficiency.

import nltk
from textblob import TextBlob
import spacy
nlp = spacy.load('en')
nlp1 = spacy.load('en_core_web_lg')

txt = """Natural language processing (NLP) is a field of computer science, artificial intelligence, and computational linguistics concerned with the interactions between computers and human (natural) languages."""

On my windows 10 2 cores, 4 processors, 8GB ram i5 hp laptop, in jupyter notebook, I ran some comparisons and here are the results.

For TextBlob:

%%time
print([w for (w, pos) in TextBlob(txt).pos_tags if pos[0] == 'N'])

And the output is

>>> ['language', 'processing', 'NLP', 'field', 'computer', 'science', 'intelligence', 'linguistics', 'inter', 'actions', 'computers', 'languages']
    Wall time: 8.01 ms #average over 20 iterations

For nltk:

%%time
print([word for (word, pos) in nltk.pos_tag(nltk.word_tokenize(txt)) if pos[0] == 'N'])

And the output is

>>> ['language', 'processing', 'NLP', 'field', 'computer', 'science', 'intelligence', 'linguistics', 'inter', 'actions', 'computers', 'languages']
    Wall time: 7.09 ms #average over 20 iterations

For spacy:

%%time
print([ent.text for ent in nlp(txt) if ent.pos_ == 'NOUN'])

And the output is

>>> ['language', 'processing', 'field', 'computer', 'science', 'intelligence', 'linguistics', 'inter', 'actions', 'computers', 'languages']
    Wall time: 30.19 ms #average over 20 iterations

It seems nltk and TextBlob are reasonably faster and this is to be expected since store nothing else about the input text, txt. Spacy is way slower. One more thing. SpaCy missed the noun NLP while nltk and TextBlob got it. I would shot for nltk or TextBlob unless there is something else I wish to extract from the input txt.


Check out a quick start into spacy here.
Check out some basics about TextBlob here.
Check out nltk HowTos here

Comely answered 26/10, 2018 at 18:15 Comment(1)
SpaCy missed NLP because it find is to be a proper noun (PNOUN). SpaCy us way slower because it has more capabilities, but you can disable the syntactic parser and speed things up quite a bit.Lavery
A
5
import nltk
lines = 'lines is some string of words'
tokenized = nltk.word_tokenize(lines)
nouns = [word for (word, pos) in nltk.pos_tag(tokenized) if(pos[:2] == 'NN')]
print (nouns)

Just simplied abit more.

Arleyne answered 28/9, 2019 at 17:40 Comment(0)
N
4

I'm not an NLP expert, but I think you're pretty close already, and there likely isn't a way to get better than quadratic time complexity in these outer loops here.

Recent versions of NLTK have a built in function that does what you're doing by hand, nltk.tag.pos_tag_sents, and it returns a list of lists of tagged words too.

Nebuchadnezzar answered 7/11, 2015 at 21:13 Comment(0)
I
4

Your code has no redundancy: You read the file once and visit each sentence, and each tagged word, exactly once. No matter how you write your code (e.g., using comprehensions), you will only be hiding the nested loops, not skipping any processing.

The only potential for improvement is in its space complexity: Instead of reading the whole file at once, you could read it in increments. But since you need to process a whole sentence at a time, it's not as simple as reading and processing one line at a time; so I wouldn't bother unless your files are whole gigabytes long; for short files it's not going to make any difference.

In short, your loops are fine. There are a thing or two in your code that you could clean up (e.g. the if clause that matches the POS tags), but it's not going to change anything efficiency-wise.

Impatient answered 9/11, 2015 at 11:58 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.