Triple
T22723470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Lekapene |
E561927
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | empress consort of Bulgaria |
C9962
|
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: empress consort of Bulgaria Context triple: [Maria Lekapene, instanceOf, empress consort of Bulgaria]
-
A.
Byzantine empress consort
chosen
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.
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.
-
C.
Empress consort of Austria
The Empress consort of Austria was the wife of the reigning Emperor of Austria, serving as the empire’s highest-ranking woman with ceremonial, social, and often dynastic responsibilities but without sovereign authority.
-
D.
Duchess consort of Austria
The Duchess consort of Austria is the wife of a reigning or titular Duke of Austria, holding the title by marriage and often performing ceremonial, social, and dynastic roles within the Austrian nobility.
-
E.
Despotess consort
A despotess consort is the spouse or partner of an absolute female ruler, wielding influence and status derived from her intimate association with the despotess’s autocratic power.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:20 p.m.