Triple
T20790431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infanta Maria Ana of Portugal |
E511758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Princess of Saxony |
C44089
|
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 Saxony Context triple: [Infanta Maria Ana of Portugal, instanceOf, Princess of Saxony]
-
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.
Electress of Saxony
The Electress of Saxony was the consort of the Elector of Saxony, a high-ranking noblewoman who held significant ceremonial, dynastic, and sometimes political influence within the Holy Roman Empire.
-
C.
Margravine of Meissen
A Margravine of Meissen is the wife or widow of the Margrave of Meissen, a noble title in the medieval and early modern Holy Roman Empire associated with the border territory (march) of Meissen in present-day eastern Germany.
-
D.
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.
-
E.
Electress of Bavaria
The Electress of Bavaria was the title held by the consort of the Elector of Bavaria, a principal ruler within the Holy Roman Empire who possessed the hereditary right to participate in the election of the emperor.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:38 p.m.