Sure! Let's consider a database for a music store. An unnormalized database for this scenario might look something like this:

Music_Store
+---------------+--------------+--------------+--------------+
| Song_Name     | Artist              | Album              | Genre            |
+---------------+--------------+--------------+--------------+
| Shape of You  | Ed Sheeran   | Divide       | Pop                         |
| Sorry               | Justin Bieber | Purpose   | Pop                         |
| Closer             | The Chainsmokers | Collage    | Electronic      |
+---------------+--------------+--------------+--------------+
However, this unnormalized database is not very efficient. In case of repetitive data, it will lead to data redundancy and data inconsistency. A normalised database for this scenario would look something like this:

Song
+---------------+
| Song_ID           |
| Song_Name     |
+---------------+

Artist
+--------------+
| Artist_ID         |
| Artist_Name  |
+--------------+

Album
+--------------+
| Album_ID         |
| Album_Name   |
+--------------+

Genre
+--------------+
| Genre_ID         |
| Genre_Name   |
+--------------+

Song_Artist
+---------------+--------------+
| Song_ID           | Artist_ID         |
+---------------+--------------+

Album_Song
+--------------+---------------+
| Album_ID        | Song_ID           |
+--------------+---------------+

Song_Genre
+---------------+--------------+
| Song_ID           | Genre_ID        |
+---------------+--------------+
In this normalised database, each table represents a different entity. The relationships between these entities are established through foreign keys. The result is a database that is more efficient, flexible, and less prone to data redundancy and data inconsistencies.
spam fails_task lang_mismatch pii not_appropriate hate_speech sexual_content quality toxicity humor helpfulness creativity violence