Triple
T19391876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matilda of Anjou |
E485089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Countess of Anjou |
C42028
|
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 Anjou Context triple: [Matilda of Anjou, instanceOf, Countess of Anjou]
-
A.
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.
-
B.
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.
-
C.
Countess of Burgundy
The Countess of Burgundy is a noblewoman who holds or is married to the holder of the feudal title governing the historic County of Burgundy, wielding significant regional authority, land rights, and dynastic influence.
-
D.
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.
-
E.
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.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:36 p.m.