Triple
T21348830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Augusta of Saxe-Weimar-Eisenach |
E526418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German Empress consort |
C19771
|
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: German Empress consort Context triple: [Princess Augusta of Saxe-Weimar-Eisenach, instanceOf, German Empress consort]
-
A.
German Empress
chosen
A German Empress is the female sovereign or consort holding the highest imperial rank within the German Empire, typically as the wife of the German Emperor.
-
B.
Queen of Germany
The Queen of Germany is a conceptual class representing the female monarch or consort who embodies the highest ceremonial, cultural, and symbolic authority within the German realm.
-
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 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.
-
E.
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.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 5:02 p.m.