Triple
T36164184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleanor Poynings |
E1045952
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Countess of Northumberland |
C65211
|
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: Countess of Northumberland Context triple: [Eleanor Poynings, instanceOf, Countess of Northumberland]
-
A.
Countess of Lancaster
The Countess of Lancaster is a noblewoman holding the comital title associated with the historic English county and honor of Lancaster, typically by marriage to or inheritance from the Earl or Duke of Lancaster.
-
B.
Countess of Leicester
The Countess of Leicester is a noblewoman who holds, by marriage or inheritance, the aristocratic title associated with the earldom of Leicester, often playing significant social, political, and dynastic roles within the English peerage.
-
C.
Countess of Welles
The Countess of Welles is a noblewoman holding the comital title associated with the Welles peerage, historically linked to the English aristocratic Welles family and their estates.
-
D.
Countess of Shrewsbury
The Countess of Shrewsbury is a noble title historically held by the wife or female counterpart of the Earl of Shrewsbury, associated with high-ranking aristocratic status and influence in English peerage.
-
E.
Countess of Arundel
The Countess of Arundel is a noblewoman holding the title associated with the Earldom of Arundel, historically signifying high-ranking aristocratic status, landholding, and influence within the English peerage.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.