Triple
T3795954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Seymour, 1st Duke of Somerset |
E89770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tudor statesman |
C11716
|
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 statesman Context triple: [Edward Seymour, 1st Duke of Somerset, instanceOf, Tudor statesman]
-
A.
13th-century English politician
A 13th-century English politician was a medieval figure involved in the governance of England, often serving in roles such as a member of Parliament, royal administrator, or local official under the monarchy.
-
B.
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.
-
C.
politician of the Stuart period
A politician of the Stuart period is a public officeholder or influential political figure active in the British Isles between 1603 and 1714, operating within the monarchical, parliamentary, and factional structures of Stuart rule.
-
D.
14th-century English noble
A 14th-century English noble is a high-ranking member of the medieval English aristocracy who holds land from the king, exercises local political and military authority, and participates in courtly and feudal obligations within a rigidly hierarchical society.
-
E.
16th-century English person
chosen
A 16th-century English person is an individual who lived in England between 1501 and 1600, experiencing the social, political, religious, and cultural transformations of the Tudor era.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.