Triple
T3867151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria of Portugal, Duchess of Parma |
E91888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | duchess consort of Parma |
C14438
|
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: duchess consort of Parma Context triple: [Maria of Portugal, Duchess of Parma, instanceOf, duchess consort of Parma]
-
A.
Duchess of Brunswick-Lüneburg
A Duchess of Brunswick-Lüneburg is a noblewoman who holds the ducal title in the historical German principality of Brunswick-Lüneburg, typically by marriage to or inheritance from a reigning duke.
-
B.
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.
-
C.
Electress of Bavaria
The Electress of Bavaria was the title held by the consort of the Elector of Bavaria, a principal ruler within the Holy Roman Empire who possessed the hereditary right to participate in the election of the emperor.
-
D.
princess of Waldeck and Pyrmont
A princess of Waldeck and Pyrmont is a female member of the German princely House of Waldeck and Pyrmont, typically by birth or marriage, bearing the associated noble title and status.
-
E.
Electress Palatine
An Electress Palatine was the wife or female consort of the Elector Palatine, a prince of the Holy Roman Empire who held the hereditary right to participate in the election of the emperor.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.