Ling 573 - Natural Language Processing Systems and Applications
Spring 2015
Deliverable #2: Baseline Summarization System
Code and Results due: April 24, 2015: 23:59
Updated Project Report due: April 28, 2015: 09:00
Goals
In this deliverable, you will implement a baseline summarization
system. You will
- Create an end-to-end summarization system going from topic-oriented document clusters to short summaries.
- Implement a content selection component, based on techniques discussed in class and in the readings to identify salient content.
- Identify the resources - software and corpus - that can support this task.
Baseline end-to-end system
For this deliverable, you will need to implement a baseline end-to-end system. You should build on approaches presented in class and readings.
You may implement any effective strategy, but you are
encouraged to implement an extractive summarization strategy.
Your system should include:
- Content selection, to determine which information to include in the summar
- Information ordering, to organize the selected content
- Content realization, to create your output summary.
Since this is a baseline system, it is not expected that your system will be
as elaborate as those presented in class. You should concentrate on "connectivity first": get the system to work end-to-end first, and then work on refinements.
Data
We will be focusing on the TAC summarization shared task. We will use
one year's data as devtest for most of the term, and then use a new unseen
year's data as final evaltest in the last deliverable.
Document Collection
The AQUAINT and AQUAINT-2 Corpora have been employed as the document
collections for the summarization task for a number of years,
and will form the basis of summarization for this deliverable.
The collections can be found on patas in /corpora/LDC/LDC02T31/ (AQUAINT, 1996-2000) and /corpora/LDC/LDC08T25/ (AQUAINT-2, 2004-2006).
Training Data
You may use any of the DUC or TAC summarization data through 2009
for training and developing your system. For previous years, there are prepared document sets and model summaries
to allow you to train and tune your
summarization system.
All model files appear in /dropbox/14-15/573/Data/models.
All document specification files appear in /dropbox/14-15/573/Data/Documents.
Training data appear in the training subdirectories and devtest data in the devtest directory.
Development Test Data
You should evaluate on the TAC-2010 topic-oriented document sets and their corresponding model summaries. You should only evaluate your system on the
the 'A' sets. Development test data appears in the devtest subdirectories.
Evaluation
You will employ the standard automatic ROUGE method to evaluate
the results from your baseline end-to-end summarization ystem.
- Evaluation results should be stored in your results directory.
- Output files should be named D2.results.
- You should provide results for ROUGE-1, ROUGE-2, ROUGE-3,and ROUGE-4 which have, in aggregate, been shown to correlate well with human assessments of responsiveness. This can be done with the "-n 4" switch in ROUGE.
Code implementing the ROUGE metric
is provided in /dropbox/14-15/573/code/ROUGE/ROUGE-1.5.5.pl. Example
configuration files are given.
- rouge_run_ex.xml gives a model configuration file covering the 2010 data.
- You will need to change the "PEER-ROOT" to point to your own outputs.
- You also adjust the "PEERS" filenames to handle differences in file naming.
- The directories and models for the model files are set correctly for the
TAC 2010 evaluation. You would to point them to alternative files/directories
if you wish to use other data, such as the 2009 data.
- To be safe, please call with perl5.10.0.
- You should use the following flag settings for your official evaluation runs:
-e ROUGE_DATA_DIR -a -n 4 -x -m -c 95 -r 1000 -f A -p 0.5 -t 0 -l 100 -s -d CONFIG_FILE_WITH_PATH
- where, ROUGE_DATA_DIR is /dropbox/14-15/573/code/ROUGE/data
- CONFIG_FILE_WITH_PATH is the location of your revised configuration file
- Output is writtent to standard output by default.
- Further usage information can be found using the -H flag or invoking ROUGE with
no parameters.
Outputs
Create a directory D2 under the outputs directory containing the summaries based on running your baseline summarization system on
the test data file.
You should do this as follows:
- Summary output
- Each summary should be well-organized, in English, using complete sentences. It should have one sentence per line. (Other formats can be used, but require modifications to the scoring configuration.) A blank line may be used to separate paragraphs, but no other formatting is allowed (such as bulleted points, tables, bold-face type, etc.). Each summary can be no longer than 100 words (whitespace-delimited tokens). Summaries over the size limit will be truncated.
- Summaries should be based only on the 'A' group of documents for each
of the topics in the specification file. All processing of documents and generation of summaries must be automatic.
- Submission format: A run will comprise exactly one file per topic summary, where the name of each summary file is the ID of its document set. Please include a file for each summary, even if the file is empty. Each file will be read and assessed as a plain text file, so no special characters or markups are allowed.
Extending the project report
This extended version should include all the sections from the
original report (with many still as stubs) and additionally
include the following new material:
- Approach
- System architecture (NOTE: We expect an architecture diagram similar to
that from the course notes, with more detail in the subcomponents. )
- Content Selection
- Information Ordering
- Content Realization
- Evaluation
- Baseline results: this subsection should describe the results of your baseline system.
- You should include a table presenting the ROUGE-1, ROUGE-2, ROUGE-3, and
ROUGE-4 scores of your system.
- You should also present some error analysis help to motivate future improvements.
Please name your report D2.pdf.
Presentation
Your presentation may be prepared in any computer-projectable format,
including HTML, PDF, PPT, and Word. Your presentation should take
about 10 minutes to cover your main content, including:
- System architecture
- Content selection
- Information Ordering
- Content Realization
- Issues and successes
- Related reading which influenced your approach
Your presentation should be deposited in your doc directory,
but it is not due until the actual presentation time. You may continue
working on it after the main deliverable is due.
Summary
- Finish coding and document all code.
- Verify that all code runs effectively on patas using Condor.
- Add any specific execution or other notes to a README.
- Create your D2.pdf and add it to the doc directory.
- Verify that all components have been added and any changes checked in.