Triple
T24733285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King's Principal Secretary |
E618345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tudor government position |
C49087
|
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 government position Context triple: [King's Principal Secretary, instanceOf, Tudor government position]
-
A.
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.
-
B.
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.
-
C.
Tudor-era noble
A Tudor-era noble is a high-ranking member of England’s aristocracy during the Tudor dynasty (1485–1603), wielding political influence, land-based wealth, and social prestige within a rigid hierarchical court and feudal system.
-
D.
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.
-
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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
Created at: April 18, 2026, 4:03 a.m.