Triple
T30192001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Thomas Pope |
E767515
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 16th-century English courtier |
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: 16th-century English courtier Context triple: [Sir Thomas Pope, instanceOf, 16th-century English courtier]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
15th-century English noblewoman
A 15th-century English noblewoman is an aristocratic woman of late medieval England whose life centers on dynastic marriage, estate management, patronage, and navigating the political and social upheavals of the Wars of the Roses.
-
E.
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.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:29 p.m.