Triple
T20723657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infanta Antónia of Portugal |
E509380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Princess of Hohenzollern |
C43500
|
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 Hohenzollern Context triple: [Infanta Antónia of Portugal, instanceOf, Princess of Hohenzollern]
-
A.
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.
-
B.
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.
-
C.
Grand Duchess of Hesse
The Grand Duchess of Hesse was the title held by the consort or, in rare cases, the reigning female sovereign of the Grand Duchy of Hesse, a former German state that existed from 1806 to 1918.
-
D.
princess of the Palatinate
A princess of the Palatinate is a female member of the ruling or formerly ruling house of the Electoral Palatinate, a historic principality of the Holy Roman Empire centered in the Rhine region of what is now Germany.
-
E.
Bavarian princess
A Bavarian princess is a noblewoman of royal or princely rank from the historical region of Bavaria, traditionally associated with the Bavarian royal or ruling families.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:28 p.m.