Triple
T38621431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleanor of Aragon, Countess of Toulouse |
E936877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Countess consort of Toulouse |
C66033
|
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 consort of Toulouse Context triple: [Eleanor of Aragon, Countess of Toulouse, instanceOf, Countess consort of Toulouse]
-
A.
Countess consort of Champagne
A Countess consort of Champagne is the wife of the reigning Count of Champagne, holding the title and associated social and ceremonial duties by marriage rather than by hereditary right.
-
B.
Duchess consort of Touraine
The Duchess consort of Touraine is the wife of the reigning or titular Duke of Touraine, holding the ducal style and social rank by marriage rather than by hereditary right.
-
C.
Countess consort of Guelders
A Countess consort of Guelders is the wife of the reigning Count of Guelders, holding the title and associated social status through marriage rather than by hereditary right.
-
D.
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.
-
E.
Countess of Champagne
The Countess of Champagne is a noblewoman who holds the hereditary or marital title associated with ruling or representing the County of Champagne within the medieval French 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.