Skip to content Skip to sidebar Skip to footer

Utilizing the Open Movie Database Api for Predicting the Review Class of Movies

How to Fix Pic Review Data for Sentiment Analysis (Text Classification)

Concluding Updated on December 21, 2020

Text information preparation is different for each problem.

Preparation starts with simple steps, like loading data, but chop-chop gets difficult with cleaning tasks that are very specific to the data yous are working with. You need help as to where to begin and what society to work through the steps from raw data to information ready for modeling.

In this tutorial, you will discover how to prepare motion-picture show review text data for sentiment assay, pace-by-step.

After completing this tutorial, you lot will know:

  • How to load text data and clean it to remove punctuation and other not-words.
  • How to develop a vocabulary, tailor it, and save information technology to file.
  • How to prepare movie reviews using cleaning and a pre-defined vocabulary and save them to new files gear up for modeling.

Kick-start your project with my new volume Deep Learning for Natural Language Processing, including step-by-step tutorials and the Python source lawmaking files for all examples.

Let's get started.

  • Update October/2017: Fixed a modest problems when skipping non-matching files, cheers Jan Zett.
  • Update Dec/2017: Fixed a small typo in total example, thanks Ray and Zain.
  • Update Aug/2020: Updated link to movie review dataset.

How to Prepare Movie Review Data for Sentiment Analysis

How to Gear up Moving-picture show Review Data for Sentiment Analysis
Photo past Kenneth Lu, some rights reserved.

Tutorial Overview

This tutorial is divided into five parts; they are:

  1. Flick Review Dataset
  2. Load Text Information
  3. Clean Text Data
  4. Develop Vocabulary
  5. Salvage Prepared Data

Need help with Deep Learning for Text Data?

Take my free 7-24-hour interval electronic mail crash course now (with code).

Click to sign-up and likewise get a free PDF Ebook version of the course.

1. Picture Review Dataset

The Movie Review Data is a collection of movie reviews retrieved from the imdb.com website in the early 2000s by Bo Pang and Lillian Lee. The reviews were collected and made bachelor as part of their research on tongue processing.

The reviews were originally released in 2002, but an updated and cleaned upwardly version was released in 2004, referred to as "v2.0".

The dataset is comprised of 1,000 positive and 1,000 negative motion picture reviews drawn from an archive of the rec.arts.movies.reviews newsgroup hosted at IMDB. The authors refer to this dataset every bit the "polarity dataset".

Our information contains 1000 positive and chiliad negative reviews all written before 2002, with a cap of 20 reviews per author (312 authors full) per category. We refer to this corpus every bit the polarity dataset.

— A Sentimental Education: Sentiment Analysis Using Subjectivity Summarization Based on Minimum Cuts, 2004.

The data has been cleaned up somewhat, for example:

  • The dataset is comprised of only English reviews.
  • All text has been converted to lowercase.
  • There is white infinite around punctuation like periods, commas, and brackets.
  • Text has been split into ane sentence per line.

The data has been used for a few related natural linguistic communication processing tasks. For nomenclature, the functioning of classical models (such as Support Vector Machines) on the data is in the range of high 70% to low lxxx% (e.g. 78%-to-82%).

More sophisticated information preparation may see results as high as 86% with x-fold cantankerous validation. This gives us a ballpark of depression-to-mid 80s if we were looking to use this dataset in experiments on modern methods.

… depending on choice of downstream polarity classifier, nosotros tin attain highly statistically meaning comeback (from 82.eight% to 86.iv%)

— A Sentimental Education: Sentiment Analysis Using Subjectivity Summarization Based on Minimum Cuts, 2004.

You can download the dataset from hither:

  • Pic Review Polarity Dataset (review_polarity.tar.gz, 3MB)

Afterward unzipping the file, you will have a directory chosen "txt_sentoken" with ii sub-directories containing the text "neg" and "pos" for negative and positive reviews. Reviews are stored one per file with a naming convention cv000 to cv999 for each of neg and pos.

Next, let's look at loading the text data.

ii. Load Text Data

In this section, we will look at loading individual text files, then processing the directories of files.

We volition assume that the review data is downloaded and available in the current working directory in the folder "txt_sentoken".

Nosotros tin load an individual text file past opening information technology, reading in the ASCII text, and endmost the file. This is standard file handling stuff. For example, we tin can load the first negative review file "cv000_29416.txt" as follows:

This loads the document as ASCII and preserves any white space, like new lines.

We can turn this into a function called load_doc() that takes a filename of the document to load and returns the text.

Nosotros take ii directories each with i,000 documents each. We can process each directory in turn by commencement getting a listing of files in the directory using the listdir() role, and then loading each file in turn.

For example, nosotros can load each document in the negative directory using the load_doc() function to do the actual loading.

Running this example prints the filename of each review after information technology is loaded.

Nosotros can turn the processing of the documents into a function also and employ it every bit a template later for developing a role to clean all documents in a folder. For example, below we ascertain a process_docs() function to do the same matter.

Now that nosotros know how to load the motion-picture show review text data, permit's look at cleaning it.

3. Make clean Text Data

In this section, we will wait at what information cleaning we might want to exercise to the movie review information.

Nosotros will presume that we will be using a bag-of-words model or mayhap a word embedding that does non require too much grooming.

Split into Tokens

First, let'south load one document and wait at the raw tokens divide by white infinite. We volition apply the load_doc() office adult in the previous section. We can use the split() function to split the loaded document into tokens separated by white infinite.

Running the example gives a dainty long list of raw tokens from the document.

Just looking at the raw tokens can give us a lot of ideas of things to try, such as:

  • Remove punctuation from words (e.g. 'what's').
  • Removing tokens that are only punctuation (e.g. '-').
  • Removing tokens that contain numbers (e.g. '10/x′).
  • Remove tokens that have i character (east.g. 'a').
  • Remove tokens that don't have much pregnant (e.chiliad. 'and')

Some ideas:

  • We tin filter out punctuation from tokens using the string translate() function.
  • We can remove tokens that are just punctuation or contain numbers by using an isalpha() cheque on each token.
  • We can remove English stop words using the list loaded using NLTK.
  • Nosotros tin can filter out brusk tokens by checking their length.

Below is an updated version of cleaning this review.

Running the example gives a much cleaner looking list of tokens

We tin put this into a function called clean_doc() and exam it on some other review, this time a positive review.

Again, the cleaning procedure seems to produce a good set of tokens, at least equally a start cut.

There are many more cleaning steps nosotros could take and I get out them to your imagination.

Adjacent, let's expect at how nosotros can manage a preferred vocabulary of tokens.

4. Develop Vocabulary

When working with predictive models of text, like a pocketbook-of-words model, there is a pressure to reduce the size of the vocabulary.

The larger the vocabulary, the more than sparse the representation of each discussion or document.

A part of preparing text for sentiment analysis involves defining and tailoring the vocabulary of words supported past the model.

Nosotros can do this past loading all of the documents in the dataset and building a set of words. We may decide to support all of these words, or perhaps discard some. The final called vocabulary can then be saved to file for after employ, such as filtering words in new documents in the future.

We can continue rail of the vocabulary in a Counter, which is a dictionary of words and their count with some additional convenience functions.

We need to develop a new function to procedure a document and add it to the vocabulary. The function needs to load a document past calling the previously developed load_doc() function. Information technology needs to make clean the loaded document using the previously developed clean_doc() function, then it needs to add all the tokens to the Counter, and update counts. We tin can do this last step by calling the update() office on the counter object.

Beneath is a part called add_doc_to_vocab() that takes equally arguments a document filename and a Counter vocabulary.

Finally, we tin can use our template in a higher place for processing all documents in a directory chosen process_docs() and update it to call add_doc_to_vocab().

We can put all of this together and develop a full vocabulary from all documents in the dataset.

Running the example creates a vocabulary with all documents in the dataset, including positive and negative reviews.

We can come across that there are a picayune over 46,000 unique words beyond all reviews and the top 3 words are 'film', 'one', and 'motion picture'.

Perhaps the least common words, those that only appear once beyond all reviews, are not predictive. Mayhap some of the most common words are not useful too.

These are good questions and really should be tested with a specific predictive model.

Generally, words that simply appear once or a few times across two,000 reviews are probably not predictive and can be removed from the vocabulary, greatly cutting down on the tokens we need to model.

We tin can do this by stepping through words and their counts and only keeping those with a count above a called threshold. Hither we will use v occurrences.

This reduces the vocabulary from 46,557 to 14,803 words, a huge drop. Perchance a minimum of 5 occurrences is likewise aggressive; you lot tin experiment with different values.

We can then save the chosen vocabulary of words to a new file. I like to save the vocabulary as ASCII with one word per line.

Beneath defines a function chosen save_list() to save a list of items, in this example, tokens to file, one per line.

The complete example for defining and saving the vocabulary is listed below.

Running this concluding snippet subsequently creating the vocabulary will salvage the chosen words to file.

It is a skillful idea to take a look at, and even study, your called vocabulary in order to get ideas for improve preparing this data, or text information in the future.

Next, we can expect at using the vocabulary to create a prepared version of the motion-picture show review dataset.

5. Save Prepared Information

We can use the data cleaning and chosen vocabulary to prepare each movie review and save the prepared versions of the reviews ready for modeling.

This is a proficient practise as it decouples the data preparation from modeling, allowing you lot to focus on modeling and circle dorsum to data prep if you take new ideas.

We can kickoff off by loading the vocabulary from 'vocab.txt'.

Next, we tin can clean the reviews, apply the loaded vocab to filter out unwanted tokens, and save the clean reviews in a new file.

One approach could exist to save all the positive reviews in one file and all the negative reviews in another file, with the filtered tokens separated by white infinite for each review on separate lines.

Offset, we can define a function to procedure a document, make clean information technology, filter it, and render it as a single line that could be saved in a file. Below defines the doc_to_line() function to do but that, taking a filename and vocabulary (every bit a gear up) as arguments.

It calls the previously defined load_doc() part to load the document and clean_doc() to tokenize the document.

Next, we can define a new version of process_docs() to step through all reviews in a folder and convert them to lines past calling doc_to_line() for each document. A list of lines is and so returned.

We can then phone call process_docs() for both the directories of positive and negative reviews, then phone call save_list() from the previous section to save each list of processed reviews to a file.

The consummate code listing is provided below.

Running the example saves ii new files, 'negative.txt' and 'positive.txt', that contain the prepared negative and positive reviews respectively.

The data is ready for use in a handbag-of-words or even word embedding model.

Extensions

This section lists some extensions that yous may wish to explore.

  • Stemming. We could reduce each word in documents to their stem using a stemming algorithm similar the Porter stemmer.
  • N-Grams. Instead of working with private words, nosotros could work with a vocabulary of word pairs, called bigrams. Nosotros could also investigate the use of larger groups, such equally triplets (trigrams) and more than (n-grams).
  • Encode Words. Instead of saving tokens as-is, we could save the integer encoding of the words, where the index of the word in the vocabulary represents a unique integer number for the word. This will brand information technology easier to work with the data when modeling.
  • Encode Documents. Instead of saving tokens in documents, we could encode the documents using a purse-of-words model and encode each word every bit a boolean present/absent-minded flag or employ more sophisticated scoring, such as TF-IDF.

If yous try whatsoever of these extensions, I'd dearest to know.
Share your results in the comments below.

Farther Reading

This department provides more resources on the topic if you lot are looking go deeper.

Papers

  • A Sentimental Education: Sentiment Analysis Using Subjectivity Summarization Based on Minimum Cuts, 2004.

APIs

  • nltk.tokenize package API
  • Chapter two, Accessing Text Corpora and Lexical Resources
  • os API Miscellaneous operating system interfaces
  • collections API – Container datatypes

Summary

In this tutorial, you discovered how to ready movie review text data for sentiment analysis, step-by-stride.

Specifically, you learned:

  • How to load text data and clean it to remove punctuation and other non-words.
  • How to develop a vocabulary, tailor information technology, and save information technology to file.
  • How to prepare moving-picture show reviews using cleaning and a predefined vocabulary and salve them to new files set for modeling.

Exercise you have whatever questions?
Ask your questions in the comments beneath and I will do my all-time to answer.

Develop Deep Learning models for Text Data Today!

Deep Learning for Natural Language Processing

Develop Your Own Text models in Minutes

...with simply a few lines of python code

Find how in my new Ebook:
Deep Learning for Natural language Processing

It provides self-written report tutorials on topics like:
Bag-of-Words, Word Embedding, Language Models, Caption Generation, Text Translation and much more...

Finally Bring Deep Learning to your Natural Language Processing Projects

Skip the Academics. Just Results.

See What's Inside

whitehousenoung1987.blogspot.com

Source: https://machinelearningmastery.com/prepare-movie-review-data-sentiment-analysis/

Postar um comentário for "Utilizing the Open Movie Database Api for Predicting the Review Class of Movies"