Triple
T31795031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabethan Poor Laws |
E811571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tudor legislation |
C2432
|
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: Tudor legislation Context triple: [Elizabethan Poor Laws, instanceOf, Tudor legislation]
-
A.
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.
-
B.
Act of Parliament of England
chosen
An Act of Parliament of England is a formal written law enacted by the English Parliament prior to the 1707 Acts of Union, having legal force within the Kingdom of England and its territories.
-
C.
medieval legislation
Medieval legislation encompasses the body of laws, decrees, and legal customs established by monarchs, feudal lords, and religious authorities in Europe during the Middle Ages to regulate social order, property, crime, and governance.
-
D.
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.
-
E.
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.
- F. None of above.
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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:40 p.m.