Triple
T1766902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elisabeth Christine of Brunswick-Wolfenbüttel |
E38783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Habsburg consort |
C2998
|
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: Habsburg consort Context triple: [Elisabeth Christine of Brunswick-Wolfenbüttel, instanceOf, Habsburg consort]
-
A.
Habsburg monarch
A Habsburg monarch is a sovereign ruler from the Habsburg dynasty, which dominated Central European and Spanish thrones for centuries through strategic marriages and dynastic inheritance.
-
B.
Holy Roman Empress consort
chosen
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.
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.
-
D.
Austrian archduchess
An Austrian archduchess is a female member of the Habsburg or Habsburg-Lorraine dynasty, traditionally bearing the noble title associated with the Archduchy of Austria and often involved in dynastic politics, court life, and diplomatic marriages.
-
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.
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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:31 p.m.