Triple
T7351659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Howard, Earl of Surrey |
E169516
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tudor-period nobleman |
C22060
|
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-period nobleman Context triple: [Henry Howard, Earl of Surrey, instanceOf, Tudor-period nobleman]
-
A.
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.
-
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.
15th-century English politician
A 15th-century English politician is a historical figure who participated in the governance and political affairs of England during the 1400s, often through roles in Parliament, royal councils, or local administration.
-
D.
member of the Tudor dynasty
A member of the Tudor dynasty is an individual belonging by blood or lawful succession to the royal house that ruled England and Wales from 1485 to 1603, originating with Henry VII and ending with Elizabeth I.
-
E.
Scottish nobleman
A Scottish nobleman is a male member of the Scottish aristocracy who holds a hereditary or granted title, land, and social status within Scotland’s traditional feudal hierarchy.
- 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_69c68a5878888190968ce4d04db8d69f |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:05 p.m.