Triple
T5172057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archduchess Auguste Ferdinande of Austria |
E116706
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bavarian royal consort |
C9157
|
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: Bavarian royal consort Context triple: [Archduchess Auguste Ferdinande of Austria, instanceOf, Bavarian royal consort]
-
A.
Bavarian princess
A Bavarian princess is a noblewoman of royal or princely rank from the historical region of Bavaria, traditionally associated with the Bavarian royal or ruling families.
-
B.
Duchess consort of Holstein-Gottorp
The Duchess consort of Holstein-Gottorp is the wife of the reigning Duke of Holstein-Gottorp, holding a ceremonial and dynastic role within the ducal house and its associated European noble networks.
-
C.
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.
-
D.
Electress of Bavaria
chosen
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.
-
E.
Archduchess of Austria
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.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:45 p.m.