Triple
T33617433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maud de Lacy, Countess of Gloucester |
E861157
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Countess of Gloucester |
C61225
|
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 Gloucester Context triple: [Maud de Lacy, Countess of Gloucester, instanceOf, Countess of Gloucester]
-
A.
Duchess of Gloucester
The Duchess of Gloucester is a British royal title traditionally granted to the wife of the Duke of Gloucester, a member of the United Kingdom’s royal family.
-
B.
Duchess of Richmond
The Duchess of Richmond is a noble title traditionally granted to the wife or female holder associated with the Duke of Richmond in the British peerage, often linked to significant social and political influence within aristocratic society.
-
C.
Countess of Kent
The Countess of Kent is a noble title historically granted to a woman, either in her own right or as the wife of the Earl of Kent, associated with the English county of Kent and its aristocratic lineage.
-
D.
Duchess of Devonshire
The Duchess of Devonshire is a noble title in the British peerage traditionally held by the wife of the Duke of Devonshire, historically associated with significant social, political, and cultural influence within aristocratic society.
-
E.
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.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.