Erato: Automatizing Poetry Evaluation

Manex Agirrezabal, Hugo Gonçalo Oliveira, Aitor Ormazabal
10/31/2023
cs.CL

No official code found. Best implementation: manexagirrezabal/erato (8 stars, last commit 2025-07-29).

Abstract

We present Erato, a framework designed to facilitate the automated evaluation of poetry, including that generated by poetry generation systems. Our framework employs a diverse set of features, and we offer a brief overview of Erato's capabilities and its potential for expansion. Using Erato, we compare and contrast human-authored poetry with automatically-generated poetry, demonstrating its effectiveness in identifying key differences. Our implementation code and software are freely available under the GNU GPLv3 license.

View on arXivView PDF

Code Implementations(1)

manexagirrezabal/eratoCommunity100%

A poetry evaluation framework

80HTML, PythonJan 28, 20221 years ago

Similar Papers

Poller: Are LLMs Suitable for Evaluating the Poetry Understanding Task?

85% match2026

Evaluating Diversity in Automatic Poetry Generation

83% match1 repo72024

Shaer: Controlled Arabic Poetry Generation with Meter Subform and Semantic Conditioning

82% match2026

Aesthetics of Sanskrit Poetry from the Perspective of Computational Linguistics: A Case Study Analysis on Siksastaka

82% match2023

Ashaar: Automatic Analysis and Generation of Arabic Poetry Using Deep Learning Approaches

81% match1 repo262023

Authorship attribution and aesthetic evaluation of AI poetry: a case study with Haiku

80% match2026

Cite this paper

@article{agirrezabal2023erato,
  title  = {Erato: Automatizing Poetry Evaluation},
  author = {Manex Agirrezabal and Hugo Gonçalo Oliveira and Aitor Ormazabal},
  year   = {2023},
  eprint = {2310.20326},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2310.20326v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2310.20326.svg)](https://codeofpaper.com/paper/2310.20326)

Discussion