Triple
T35092428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Palaiologina Kantakouzene |
E1012767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Bulgarian royal consort |
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: medieval Bulgarian royal consort Context triple: [Maria Palaiologina Kantakouzene, instanceOf, medieval Bulgarian royal consort]
-
A.
medieval Bulgarian noblewoman
A medieval Bulgarian noblewoman is an aristocratic female member of Bulgarian society during the Middle Ages, typically associated with landownership, political influence, and participation in courtly and religious life.
-
B.
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.
-
C.
Bithynian royal consort
A Bithynian royal consort is the spouse or recognized partner of a reigning king of Bithynia, holding a prominent position within the Hellenistic court and dynastic structure of the ancient Bithynian kingdom.
-
D.
Hungarian queen consort
A Hungarian queen consort is the wife of a reigning king of Hungary, holding the title of queen and performing ceremonial, dynastic, and sometimes political roles without exercising sovereign authority in her own right.
-
E.
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.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.