1 / 28

SIMS 290-2: Applied Natural Language Processing

SIMS 290-2: Applied Natural Language Processing. Marti Hearst Sept 1, 2004. Today. How shall we transform a huge text collection? Levels of Language Intro to NLTK and Python. The Enron Email Archive. Background

cain
Télécharger la présentation

SIMS 290-2: Applied Natural Language Processing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. SIMS 290-2: Applied Natural Language Processing Marti Hearst Sept 1, 2004

  2. Today • How shall we transform a huge text collection? • Levels of Language • Intro to NLTK and Python

  3. The Enron Email Archive • Background • Originally made public, and posted to the web by the Federal Energy Regulatory Commission during its investigation. • ~500,000 messages • Salon article: http://www.salon.com/news/feature/2003/10/14/enron/index_np.html • Later purchased by Leslie Kaelbling at MIT • People at SRI, notably Melinda Gervasio, cleaned it up • No attachments • Some messages have been deleted "as part of a redaction effort due to requests from affected employees". • Invalid email addresses were converted to user@enron.com • Posted online for research on email by William Cohen at • http://www-2.cs.cmu.edu/~enron/ • Paper describing the dataset: • The Enron Corpus: A New Dataset for Email Classification Research, Klimt and Yang, ECML 2004 http://www-2.cs.cmu.edu/~bklimt/papers/2004_klimt_ecml.pdf

  4. The Enron Email Archive • A valuable resource • No other large open email corpus for research • A sensitive resource • We need to be respectful and careful about how we treat this information • We can add value • Idea: this class produces something more valuable and interesting than what we started with. • Researchers and practitioners will build on our results

  5. The Enron Email Archive • So … what’s in there? • 500,000 messages. • Let’s search (on a subset of the collection): http://quasi.berkeley.edu/anlp/enron_search.html • Now … what more would we like to have?

  6. Levels of Language • Sound Structure (Phonetics and Phonology) • The sounds of speech and their production • The systematic way that sounds are differently realized in different environments. • Word Structure (Morphology) • From morphos = shape (not transform, as in morph) • Analyzes how words are formed from minimal units of meaning; also derivational rules • dog + s = dogs; eat, eats, ate • Phrase Structure (Syntax) • From the Greek syntaxis, arrange together • Describes grammatical arrangements of words into hierarchical structure Slide adapted from Robert Berwick's

  7. Levels of Language • Thematic Structure • Getting closer to meaning • Who did what to whom • Subject, object, predicate • Semantic Structure • How the lower levels combine to convey meaning • Pragmatics and Discourse Structure • How language is used across sentences. Slide adapted from Robert Berwick's

  8. Parsing at Every Level • Transforming from a surface representation to an underlying representation • It’s not straightforward to do any of these mappings! • Ambiguity at every level • Word: is “saw” a verb or noun? • Phrase: “I saw the guy on the hill with the telescope.” • Who is on the hill? • Semantic: which hill? Slide adapted from Robert Berwick's

  9. Python and NLTK The following slides from Diane Litman’s lecture

  10. Python and Natural Language Processing • Python is a great language for NLP: • Simple • Easy to debug: • Exceptions • Interpreted language • Easy to structure • Modules • Object oriented programming • Powerful string manipulation Slide by Diane Litman

  11. Modules and Packages Python modules “package program code and data for reuse.” (Lutz) Similar to library in C, package in Java. Python packages are hierarchical modules (i.e., modules that contain other modules). Three commands for accessing modules: import from…import reload Slide by Diane Litman

  12. Modules and Packages: import • The importcommand loads a module: # Load the regular expression module >>> import re • To access the contents of a module, use dotted names: # Use the search method from the re module >>> re.search(‘\w+’, str) • To list the contents of a module, use dir: >>> dir(re) [‘DOTALL’, ‘I’, ‘IGNORECASE’,…] Slide by Diane Litman

  13. Modules and Packagesfrom…import • The from…import command loads individual functions and objects from a module: # Load the search function from the re module >>> from re import search • Once an individual function or object is loaded with from…import,it can be used directly: # Use the search method from the re module >>> search (‘\w+’, str) Slide by Diane Litman

  14. Import Keeps module functions separate from user functions. Requires the use of dotted names. Works with reload. from…import Puts module functions and user functions together. More convenient names. Does not work with reload. Import vs. from…import Slide by Diane Litman

  15. Modules and Packages: reload • If you edit a module, you must use the reload command before the changes become visible in Python: >>> import mymodule ... >>> reload (mymodule) • The reload command only affects modules that have been loaded with import; it does not update individual functions and objects loaded with from...import. Slide by Diane Litman

  16. Introduction to NLTK • The Natural Language Toolkit (NLTK) provides: • Basic classes for representing data relevant to natural language processing. • Standard interfaces for performing tasks, such as tokenization, tagging, and parsing. • Standard implementations of each task, which can be combined to solve complex problems. Slide by Diane Litman

  17. NLTK: Example Modules • nltk.token: processing individual elements of text, such as words or sentences. • nltk.probability: modeling frequency distributions and probabilistic systems. • nltk.tagger: tagging tokens with supplemental information, such as parts of speech or wordnet sense tags. • nltk.parser: high-level interface for parsing texts. • nltk.chartparser: a chart-based implementation of the parser interface. • nltk.chunkparser: a regular-expression based surface parser. Slide by Diane Litman

  18. NLTK: Top-Level Organization • NLTK is organized as a flat hierarchy of packages and modules. • Each module provides the tools necessary to address a specific task • Modules contain two types of classes: • Data-oriented classes are used to represent information relevant to natural language processing. • Task-oriented classes encapsulate the resources and methods needed to perform a specific task. Slide by Diane Litman

  19. To the First Tutorials • Tokens and Tokenization • Frequency Distributions Slide by Diane Litman

  20. The Token Module • It is often useful to think of a text in terms of smaller elements, such as words or sentences. • The nltk.token module defines classes for representing and processing these smaller elements. • What might be other useful smaller elements? Slide by Diane Litman

  21. Tokens and Types • The term word can be used in two different ways: • To refer to an individual occurrence of a word • To refer to an abstract vocabulary item • For example, the sentence “my dog likes his dog” contains five occurrences of words, but four vocabulary items. • To avoid confusion use more precise terminology: • Word token: an occurrence of a word • Word Type: a vocabulary item Slide by Diane Litman

  22. Tokens and Types (continued) • In NLTK, tokens are constructed from their types using the Token constructor: • >>> from nltk.token import * • >>> my_word= 'dog' • >>> my_word_token =Token(TEXT=my_word) ‘dog'@[?] Slide by Diane Litman

  23. Text Locations • A text location @ [s:e] specifies a region of a text: • s is the start index • e is the end index • The text location @ [s:e]specifies the text beginning at s, and including everything up to (but not including) the text at e. • This definition is consistent with Python slice. • Think of indices as appearing between elements: I saw a man 0 1 2 3 4 • Shorthand notation when location width = 1. Slide by Diane Litman

  24. Text Locations (continued) • Indices can be based on different units: • character • word • sentence • Locations can be tagged with sources (files, other text locations – e.g., the first word of the first sentence in the file) • Location member functions: • start • end • unit • source Slide by Diane Litman

  25. Tokenization • The simplest way to represent a text is with a single string. • Difficult to process text in this format. • Often, it is more convenient to work with a list of tokens. • The task of converting a text from a single string to a list of tokens is known as tokenization. Slide by Diane Litman

  26. Tokenization (continued) • Tokenization is harder that it seems I’ll see you in New York. The aluminum-export ban. • The simplest approach is to use “graphic words” (i.e., separate words using whitespace) • Another approach is to use regular expressions to specify which substrings are valid words. • NLTK provides a generic tokenization interface: TokenizerI Slide by Diane Litman

  27. TokenizerI • Defines a single method, tokenize, which takes a string and returns a list of tokens • Tokenize is independent of the level of tokenization and the implementation algorithm Slide by Diane Litman

  28. For Next Week • Monday: holiday, no class • Kevin is still installing the software • I will send email with details when ready • Probably by the end of today • Sign up for the email list! • Mail to: majordomo@sims.berkeley.edu • Put in msg body: subscribe anlp • For Wed Sept 8 • Do exercises 1-3 in Tutorial 2 (Tokenizing) • http://nltk.sourceforge.net/tutorial/introduction/nochunks.html

More Related