Triple
T6013238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria, Princess Royal |
E133884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Queen consort of Prussia |
C17644
|
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 Prussia Context triple: [Victoria, Princess Royal, instanceOf, Queen consort of Prussia]
-
A.
Duchess consort of Holstein-Gottorp
The Duchess consort of Holstein-Gottorp is the wife of the reigning Duke of Holstein-Gottorp, holding a ceremonial and dynastic role within the ducal house and its associated European noble networks.
-
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.
Princess of Prussia
chosen
A Princess of Prussia is a female member of the Prussian royal family, typically by birth or marriage, bearing the title associated with the historical Kingdom of Prussia.
-
D.
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.
-
E.
Empress consort of Russia
The Empress consort of Russia was the wife of the reigning Russian emperor (tsar), holding a high ceremonial and social status at court, often influencing politics, culture, and dynastic affairs without ruling in her own right.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:06 p.m.