Triple
T8187541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilhelmine Amalie of Brunswick-Lüneburg |
E191223
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Queen of the Romans 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: Queen of the Romans consort Context triple: [Wilhelmine Amalie of Brunswick-Lüneburg, instanceOf, Queen of the Romans consort]
-
A.
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.
-
B.
Byzantine empress consort
A Byzantine empress consort was the wife of a reigning Byzantine emperor who held significant ceremonial, political, and sometimes religious influence at the imperial court, though her authority was formally derived from her marriage rather than direct rule.
-
C.
Roman empress
A Roman empress is the wife or female counterpart of a Roman emperor, often wielding significant political, social, and cultural influence within the imperial court and broader empire.
-
D.
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.
-
E.
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.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:41 p.m.