Triple
T6944725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bianca Maria Sforza |
E160766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Queen consort of the Romans |
C2998
|
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 the Romans Context triple: [Bianca Maria Sforza, instanceOf, Queen consort of the Romans]
-
A.
Byzantine empress consort
A Byzantine empress consort was the wife of a reigning Byzantine emperor who held significant ceremonial, political, and sometimes religious influence at the imperial court, though her authority was formally derived from her marriage rather than direct rule.
-
B.
Holy Roman Empress consort
chosen
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.
-
C.
Roman empress
A Roman empress is the wife or female counterpart of a Roman emperor, often wielding significant political, social, and cultural influence within the imperial court and broader empire.
-
D.
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.
-
E.
Byzantine empress
A Byzantine empress is the imperial consort or reigning female sovereign of the Byzantine Empire, wielding varying degrees of political, ceremonial, and cultural influence within the court and empire.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:28 p.m.