Triple
T12415811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dessislava |
E296632
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Bulgarian noblewoman |
C31434
|
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 noblewoman Context triple: [Dessislava, instanceOf, medieval Bulgarian noblewoman]
-
A.
medieval Georgian noblewoman
A medieval Georgian noblewoman is an aristocratic woman of the Georgian kingdoms who held social status, land-related privileges, and dynastic responsibilities within the feudal and courtly structures of the Middle Ages.
-
B.
Serbian noblewoman
A Serbian noblewoman is a high-born woman from Serbian society, historically belonging to the aristocracy and often involved in political, cultural, or social affairs of her time.
-
C.
Byzantine noblewoman
A Byzantine noblewoman is an elite woman of the Eastern Roman Empire, distinguished by her high social rank, wealth, and influence within the imperial court, religious life, and family alliances.
-
D.
11th-century noblewoman
An 11th-century noblewoman is a high-born female member of medieval European aristocracy whose life centers on managing estates, forging political alliances through marriage, and upholding social and religious obligations within a feudal hierarchy.
-
E.
Romanian noblewoman
A Romanian noblewoman is a high-born woman from Romania’s historical aristocracy, often associated with landownership, political influence, and the preservation of regional cultural traditions.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:55 p.m.