Triple
T10018212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helena Kantakouzene |
E199549
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine noblewoman |
C27291
|
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: Byzantine noblewoman Context triple: [Helena Kantakouzene, instanceOf, Byzantine noblewoman]
-
A.
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.
-
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.
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.
-
E.
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.
- 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_69ca8315a1a08190ab310f25620f362b |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 8:53 p.m.