Triple
T21459595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ida of Chiny |
E529435
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | noblewoman of the Holy Roman Empire |
C44798
|
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: noblewoman of the Holy Roman Empire Context triple: [Ida of Chiny, instanceOf, noblewoman of the Holy Roman Empire]
-
A.
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.
-
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.
Prussian noblewoman
A Prussian noblewoman is an aristocratic woman from the historical Kingdom of Prussia, typically characterized by her high social rank, landowning family background, and adherence to the conservative, militaristic, and courtly traditions of Prussian society.
-
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. 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:08 p.m.