The Story in Three Lines
Kabuki loses nothing when you know the story in advance. Start with just three lines.
- 01
The title means release from worldly attachment. Its subject is the lingering resentment of the warrior Kagekiyo, unquiet even in death.
- 02
Danjūrō IV is said to have premiered it in 1760, playing the ghost of Kagekiyo.
- 03
The ghost first appeared in the form of a young woman before revealing its true nature; long unperformed, the play was revived in 1915.
Three Things to Watch For
These three points are all the preparation you need. On the day, simply give yourself to the stage.
A ghost in disguise
From maiden to revealed specter—soft grace flipping into aragoto force within a single performer.
Kagekiyo returns
The hero who broke the prison in Kagekiyo returns beyond death; across the eighteen, his figure echoes from play to play.
Deliverance as an ending
The title points not to vengeance unleashed but to attachment released—an ending that moves toward peace.
Characters
- The ghost of Kagekiyo
- The spirit of the Heike warrior, still bound by attachment, said to have first appeared in the borrowed form of a young woman.
Stagecraft and Highlights
Said to have been first performed by Danjūrō IV in 1760, staged so that the ghost appeared first as a young woman, letting resentment seep through before showing its true form.
After a long absence it was revived by Ichikawa Sadanji II in 1915, and later stagings have continued the attempt to render a spirit's passion through pure theatrical form.
The Ichikawa Connection
One of the Kabuki Jūhachiban, associated with Danjūrō IV; together with Kagekiyo and Kamahige it attests to the family's deep bond with the hero Kagekiyo.
Related terms
Sources
- Author
- KABUKI Universe Editorial Team
- Supervision
- Ichikawa Danjūrō
- Published
- Aug 15, 2026
- Updated
- Sep 9, 2026
Supervision means Ichikawa Danjūrō has reviewed this page's intent and key points. The text is the editorial team's writing, not Ichikawa Danjūrō's own statements. Editorial responsibility rests with the team, which corrects any error. Read the editorial policy