Triple
T10277703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Ludovika of Austria-Este |
E241011
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archduchess by marriage |
C2996
|
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: archduchess by marriage Context triple: [Maria Ludovika of Austria-Este, instanceOf, archduchess by marriage]
-
A.
Archduchess of Austria
chosen
The Archduchess of Austria is a noble title historically borne by female members of the Habsburg dynasty, denoting their status as princesses of the Austrian hereditary lands within the Holy Roman Empire and later the Austro-Hungarian Empire.
-
B.
Holy Roman Empress consort
A Holy Roman Empress consort is the wife of a reigning Holy Roman Emperor, holding the empire’s highest female title and often exercising ceremonial, dynastic, and sometimes political influence within the Holy Roman Empire.
-
C.
Bavarian queen consort
A Bavarian queen consort is the wife of a reigning king of Bavaria, holding the ceremonial and social role of queen without exercising sovereign authority.
-
D.
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.
-
E.
Electress of the Holy Roman Empire
The Electress of the Holy Roman Empire was the consort of a prince-elector, holding a prestigious dynastic and ceremonial role within the imperial hierarchy, often influencing court politics and succession.
- F. None of above.
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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:37 a.m.