Triple
T32427598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cunigunde of Luxembourg |
E828619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | queen consort of Germany |
C22825
|
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 consort of Germany Context triple: [Cunigunde of Luxembourg, instanceOf, queen consort of Germany]
-
A.
Queen of Germany
chosen
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.
-
B.
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.
-
C.
Crown Princess of Germany
The Crown Princess of Germany is the wife of the German Crown Prince, serving as the highest-ranking woman in the imperial succession hierarchy and representing the monarchy in ceremonial and social functions.
-
D.
Duchess consort of Mecklenburg
A Duchess consort of Mecklenburg is the wife of a reigning Duke of Mecklenburg, holding the ducal title by marriage and often performing ceremonial, social, and dynastic roles within the duchy.
-
E.
Queen of Prussia
The Queen of Prussia was the title held by the wife or consort of the reigning King of Prussia, serving as the kingdom’s foremost female royal figure and often playing significant political, cultural, and diplomatic roles within the Prussian and later German realms.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:54 a.m.