Triple
T25508734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penelope Devereux |
E639314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Elizabethan noblewoman |
C36280
|
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: Elizabethan noblewoman Context triple: [Penelope Devereux, instanceOf, Elizabethan noblewoman]
-
A.
Renaissance noblewoman
chosen
A Renaissance noblewoman is an elite woman of the 14th–17th centuries whose life is shaped by courtly culture, dynastic politics, patronage of the arts, and strict social and gender hierarchies.
-
B.
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.
-
C.
15th-century noblewoman
A 15th-century noblewoman is an aristocratic woman of high social rank whose life is shaped by dynastic marriage, estate management, courtly culture, and the political and religious structures of late medieval Europe.
-
D.
Countess of Pembroke
The Countess of Pembroke is a noblewoman holding the hereditary or life title associated with the Earldom of Pembroke, historically linked to high social rank, political influence, and patronage within the English aristocracy.
-
E.
14th-century English noblewoman
A 14th-century English noblewoman is an aristocratic woman of medieval England who holds social status and influence through birth or marriage, managing estates, patronage, and family alliances within a feudal and patriarchal 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:48 p.m.