Triple
T8603775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Blount |
E203745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mistress of Henry VIII |
C5727
|
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: mistress of Henry VIII Context triple: [Elizabeth Blount, instanceOf, mistress of Henry VIII]
-
A.
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.
-
B.
royal mistress
chosen
A royal mistress is a woman who maintains a long-term, often publicly acknowledged romantic and/or sexual relationship with a reigning monarch or high-ranking royal outside of marriage, sometimes wielding significant social or political influence.
-
C.
12th-century English queen consort
A 12th-century English queen consort is the wife of an English king during the 1100s, serving as a political partner, dynastic link, and influential figure in courtly, diplomatic, and sometimes religious affairs.
-
D.
mistress of Louis XIV
The mistress of Louis XIV is a woman who held an intimate, often influential relationship with the French king, frequently wielding social, cultural, and political power at his court.
-
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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:24 p.m.