Triple
T33482338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedwig Sophia |
E857510
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | princess of Brandenburg |
C61391
|
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: princess of Brandenburg Context triple: [Hedwig Sophia, instanceOf, princess of Brandenburg]
-
A.
Princess of Anhalt-Dessau
A Princess of Anhalt-Dessau is a female member of the ruling House of Ascania in the historical German principality of Anhalt-Dessau, typically by birth or marriage, holding dynastic and ceremonial status within the principality’s nobility.
-
B.
Princess of Prussia
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.
-
C.
Princess of Saxony
A Princess of Saxony is a female member of the royal or ducal house historically ruling the region of Saxony, typically bearing the title by birth or marriage within that dynasty.
-
D.
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.
-
E.
princess of Saxe-Altenburg
A princess of Saxe-Altenburg is a female member of the German ducal House of Saxe-Altenburg, typically by birth or marriage, holding the title associated with this former Ernestine duchy in Thuringia.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.