Summarization › Summary

Text summarization spans a spectrum from simple sentence selection to sophisticated language generation. Extractive methods like TextRank identify the most central sentences through graph-based ranking, modeling the insight that importance is relational rather than intrinsic. MMR improves on pure ranking by ensuring the selected sentences cover diverse aspects of the content, balancing relevance against redundancy through the lambda parameter. Neural extractive methods extend this further by using contextual embeddings to capture semantic meaning rather than surface word overlap.

Abstractive methods, built on seq2seq architectures with attention and copy mechanisms, can paraphrase and compress information more effectively than any extractive approach. The attention mechanism allows the decoder to selectively read relevant parts of the source at each generation step, the copy mechanism enables faithful reproduction of rare terms and proper names, and the coverage mechanism prevents repetition. Large pretrained models like BART and T5 bring broad language understanding to the summarization task, enabling higher quality output at the cost of substantial computational resources.

Evaluation remains a central challenge. ROUGE measures n-gram overlap with human references and is cheap but imperfectly correlated with human quality judgments. BERTScore uses semantic similarity from contextual embeddings to capture paraphrase equivalence. Human evaluation across dimensions of faithfulness, relevance, coherence, and fluency provides the most reliable quality signal but is expensive to collect at scale. The current lack of a single trusted automatic metric makes rigorous system comparison difficult and creates incentives for metric gaming.

The applications of summarization span single documents, multi-document sets, query-focused retrieval, dialogue, and headline generation, each bringing distinct structural challenges. As you build summarization systems, the most important design decisions are: which faithfulness-fluency tradeoff to accept (extractive is safer, abstractive is more powerful), how to handle domain mismatch between training data and deployment context, what evaluation criteria matter most for your use case, and how to verify that summaries are faithful before they enter production pipelines where errors can propagate.

In the next chapter, we turn to question answering, where many of the same foundations apply but the task shifts from condensing information to precisely locating and extracting specific answers.