← Latest papers
💬 NLP

Automatic Classification of Arabic Literature into Historical Eras

This paper addresses the gap in automatic classification of Arabic literature by time period beyond poetry, employing neural networks and deep learning to evaluate models on datasets spanning from the pre-Islamic to the modern era, achieving high performance in binary classification but significantly lower accuracy in fine-grained multi-era tasks.

Original authors: Zainab Alhathloul, Irfan Ahmad

Published 2026-01-23
📖 5 min read🧠 Deep dive

Original authors: Zainab Alhathloul, Irfan Ahmad

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine the Arabic language as a massive, ancient river that has been flowing for 1,500 years. Over time, the water changes: new fish appear, old ones disappear, and the current shifts speed and direction. Sometimes, a word that meant "food" in ancient times comes to mean "culture" or "poetry" centuries later.

This paper is like a team of digital detectives trying to figure out when a specific drop of water (a text) came from just by looking at it. They want to automatically sort Arabic books and poems into their correct historical eras, from the time before Islam up to the modern day.

Here is the story of their investigation, explained simply:

The Mystery: Sorting the River

Historians and linguists have already drawn a map of this river, dividing it into eras like "Pre-Islamic," "Islamic," "Abbasid," and "Modern." But doing this by hand is slow and hard. The researchers asked: Can a computer learn to do this automatically?

They tested two different "libraries" of text:

  1. The "Prose" Library (OpenITI): A huge collection of books, essays, and religious texts.
  2. The "Poetry" Library (APCD): A collection of verses from famous poets.

The Tools: Two Types of Digital Brains

To solve the mystery, the team built two types of computer "brains" (neural networks):

  • The "Bag of Words" Brain (ANN): This looks at a text like a jar of marbles. It counts how many times specific words appear but doesn't care about the order they come in. It's like judging a soup just by counting the carrots and potatoes, ignoring the recipe.
  • The "Storyteller" Brain (RNN): This reads the text like a story, word by word, remembering what came before. It understands the flow and sequence, which is crucial for language.

The Experiment: Two Ways to Play

The researchers tested these brains in two different game modes to see if the computer was just memorizing the authors or actually learning the era:

  1. The "Same Author" Mode: The computer studied a specific author's writing in the training phase and then had to guess the era of that same author's writing later. (This is like learning to recognize a friend's handwriting).
  2. The "Stranger" Mode: The computer studied a group of authors but was tested on completely different authors it had never seen before. (This is like trying to guess the decade of a song just by listening to a new band, without knowing who they are).

The Findings: What Worked and What Didn't

1. The "Stranger" Mode was Harder
When the computer had to guess the era of a writer it had never met, it struggled more. This makes sense: if you can't rely on recognizing a specific author's style, you have to rely purely on the "vibe" of the time period.

  • Result: The "Same Author" mode got much higher scores. This proves that author style is a huge clue. If the computer knows the author, it can guess the era much easier.

2. Poetry vs. Prose

  • Poetry was easier to date. The computer was better at sorting poems than prose. The researchers think this is because poems have a very rich, specific vocabulary. It's like trying to guess the year of a song based on its lyrics; the slang and rhymes change very distinctly over time.
  • Prose was trickier. Non-poetry texts (like history books) are more consistent and change more slowly, making the "time travel" harder for the computer.

3. The "Blurred Lines" Problem
The biggest challenge wasn't the computer's intelligence; it was the history itself. The boundaries between eras aren't sharp lines; they are fuzzy, gray areas.

  • Analogy: Imagine trying to tell the difference between "dawn" and "sunrise." It's a gradual shift. The computer often confused the "Islamic" era with the "Abbasid" era, or "Ottoman" with "Modern," because the language didn't change overnight. It drifted slowly.
  • Result: When the researchers asked the computer to make very fine distinctions (like 15 different time periods), it got confused. But when they asked for broad categories (like just "Old" vs. "New"), it did very well.

4. Cleaning the Data
The researchers tried "cleaning" the text by removing common words (like "the" or "and") and simplifying complex word forms.

  • Surprise: For the prose library, cleaning the text didn't help. The computer actually did better with the "messy" original text.
  • Exception: For poetry, cleaning the text did help, likely because poems use so many different forms of the same word that simplifying them made the patterns clearer.

The Bottom Line

The paper concludes that while it is possible for a computer to automatically tell which historical era an Arabic text belongs to, it is a tough job.

  • It works best when the computer knows the author.
  • It works better with poetry than with regular books.
  • It struggles when the time periods are too close together because the language changes too gradually.

The researchers didn't claim this technology is ready to replace historians or solve all dating mysteries. Instead, they showed that we can build a tool that is "better than random guessing" and helps us see the gradual evolution of the Arabic language, much like watching the river flow change over centuries.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →