Triple
T23874679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide of Savoy |
E592831
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Electress consort of Bavaria |
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: Electress consort of Bavaria Context triple: [Adelaide of Savoy, instanceOf, Electress consort of Bavaria]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Duchess consort of Austria
The Duchess consort of Austria is the wife of a reigning or titular Duke of Austria, holding the title by marriage and often performing ceremonial, social, and dynastic roles within the Austrian nobility.
-
E.
Grand Duchess consort of Baden
The Grand Duchess consort of Baden is the wife of the reigning Grand Duke of Baden, holding a ceremonial and social role within the grand ducal court and representing the grand duchy in dynastic and public functions.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 8:15 p.m.