Triple
T17900903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsaritsa Irina |
E447573
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bulgarian empress |
C29842
|
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: Bulgarian empress Context triple: [Tsaritsa Irina, instanceOf, Bulgarian empress]
-
A.
Tsaritsa of Bulgaria
chosen
The Tsaritsa of Bulgaria is the title given to the queen consort or reigning queen of Bulgaria, traditionally the wife of the Bulgarian tsar, who holds a prominent ceremonial and dynastic role in the Bulgarian monarchy.
-
B.
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.
-
C.
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.
-
D.
Bulgarian noblewoman
A Bulgarian noblewoman is a high-born woman from Bulgaria’s aristocratic or ruling classes, historically associated with landownership, political influence, and cultural patronage.
-
E.
Empress of Russia
The Empress of Russia is the female sovereign ruler or consort at the apex of the Russian imperial hierarchy, embodying supreme political authority, dynastic continuity, and ceremonial leadership within the Russian 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:19 a.m.