Triple
T22605297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigilantia |
E566539
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mother of a Byzantine emperor |
C36400
|
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: mother of a Byzantine emperor Context triple: [Vigilantia, instanceOf, mother of a Byzantine emperor]
-
A.
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.
-
B.
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.
-
C.
member of Byzantine imperial family
chosen
A member of the Byzantine imperial family is an individual related by blood, marriage, or adoption to the reigning emperor, often holding elevated social status, political influence, and potential claims to the throne within the Byzantine Empire.
-
D.
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.
-
E.
Byzantine princess
A Byzantine princess is a high-born woman of the Eastern Roman (Byzantine) imperial family, often serving as a key figure in dynastic politics, diplomacy, and courtly culture.
- 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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 2:53 p.m.