Triple
T12335533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippa of Hainault |
E294075
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Countess of Holland |
C31316
|
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 Holland Context triple: [Philippa of Hainault, instanceOf, Countess of Holland]
-
A.
Duchess of Burgundy
The Duchess of Burgundy is a high-ranking noblewoman who holds the ducal title of Burgundy, often wielding significant political influence, overseeing courtly affairs, and managing the territories and alliances associated with the Burgundian domain.
-
B.
Countess of Blois
The Countess of Blois is a noblewoman who holds, by birth or marriage, the comital title associated with the medieval French county of Blois, often playing significant political, dynastic, and social roles within the region’s aristocracy.
-
C.
Duchess of Courland
The Duchess of Courland is a noblewoman holding the ducal title associated with the historical Duchy of Courland, often linked to its governance, dynastic alliances, and representation at European courts.
-
D.
Countess of Angoulême
The Countess of Angoulême is a noble title historically granted to the female ruler or consort associated with the County of Angoulême in southwestern France, often linked to influential medieval and early modern European dynasties.
-
E.
Duchess of Savoy
The Duchess of Savoy is a noblewoman who holds the ducal consort or sovereign title associated with the historical Duchy of Savoy, often playing significant political, dynastic, and ceremonial roles within European aristocracy.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.