Triple
T10122716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elisabeth of Bavaria |
E223335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Electress of Saxony |
C27454
|
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 of Saxony Context triple: [Elisabeth of Bavaria, instanceOf, Electress of Saxony]
-
A.
Electress of Brandenburg
The Electress of Brandenburg was the consort of the Prince-elector of Brandenburg within the Holy Roman Empire, holding a prominent dynastic and ceremonial role that often included influence in court politics, patronage, and regional governance.
-
B.
Electress of Bavaria
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 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.
-
D.
Duchess of Courland
The Duchess of Courland is a noblewoman holding the ducal title associated with the historical Duchy of Courland, often linked to its governance, dynastic alliances, and representation at European courts.
-
E.
Duchess of Brunswick-Lüneburg
A Duchess of Brunswick-Lüneburg is a noblewoman who holds the ducal title in the historical German principality of Brunswick-Lüneburg, typically by marriage to or inheritance from a reigning duke.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:05 p.m.