Triple
T28154989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legislative and Regulatory Reform Act 2006 order-making powers |
E714718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Henry VIII power |
C54478
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Henry VIII power Context triple: [Legislative and Regulatory Reform Act 2006 order-making powers, instanceOf, Henry VIII power]
-
A.
Tudor monarch
A Tudor monarch is a ruler from the English royal House of Tudor (1485–1603), characterized by strong centralized authority, religious upheaval, and significant cultural and political transformation in England.
-
B.
Tudor court
The Tudor court is the royal household and political center surrounding the Tudor monarchs of England, where power, patronage, ceremony, and intrigue shaped governance and culture in the 16th century.
-
C.
Tudor government position
A Tudor government position is an official role within the administrative, legal, or financial structures of England during the Tudor dynasty (1485–1603), responsible for implementing royal authority and managing state affairs.
-
D.
Tudor historiography
Tudor historiography is the body of historical writing and interpretation that examines the politics, religion, society, and culture of England under the Tudor dynasty (1485–1603), as well as the evolving ways historians have understood and debated this period.
-
E.
Tudor-period nobleman
A Tudor-period nobleman is a high-ranking member of the English aristocracy between 1485 and 1603, wielding political influence, land-based wealth, and social authority under the Tudor monarchy.
- F. None of above. chosen
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:02 p.m.