Jump to ContentJump to Main Navigation
Courting SanctityHoly Women and the Capetians$
Users without a subscription are not able to see the full content.

Sean L. Field

Print publication date: 2019

Print ISBN-13: 9781501736193

Published to Cornell Scholarship Online: January 2020

DOI: 10.7591/cornell/9781501736193.001.0001

Show Summary Details
Page of

PRINTED FROM Cornell University Press SCHOLARSHIP ONLINE (www.cornell.universitypressscholarship.com). (c) Copyright University of Cornell University Press, 2021. All Rights Reserved. An individual user may print out a PDF of a single chapter of a monograph in Cornell for personal use. date: 28 September 2021

Elizabeth of Spalbeek

Elizabeth of Spalbeek

A Prince’s Death, a Queen’s Crime, and a King’s Sin

(p.83) Chapter 3 Elizabeth of Spalbeek
Courting Sanctity

Sean L. Field

Cornell University Press

Elizabeth of Spalbeek was already a well-known if controversial visionary by 1276. In that year a prophecy was attributed to her in which she claimed that God was angry with King Philip III because of the king’s sins against nature. The papal legate Simon of Brie verified that he had heard a similar rumor. In the course of four separate missions to question Elizabeth, the party of Pierre de La Broce and Bishop Pierre de Benais also attributed to her the prophetic claim that Queen Marie of Brabant had poisoned her stepson, the heir to the throne. In the end Elizabeth relied on staunch denial, and chose to silence her own prophetic voice to avoid censure.

Keywords:   Elizabeth of Spalbeek, Simon of Brie, King Philip III of France, Queen Marie of Brabant, Pierre de la Broce, Pierre de Benais, prophecy

Cornell Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs, and if you can't find the answer there, please contact us.