Triple
T1703328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helena Dragaš |
E36814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine royal consort |
C9319
|
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 royal consort Context triple: [Helena Dragaš, instanceOf, Byzantine royal consort]
-
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.
royal consort
chosen
A royal consort is the spouse of a reigning monarch who holds a recognized position at court, often with ceremonial duties but typically without sovereign authority.
-
C.
Holy Roman Empress consort
A Holy Roman Empress consort is the wife of a reigning Holy Roman Emperor, holding the empire’s highest female title and often exercising ceremonial, dynastic, and sometimes political influence within the Holy Roman Empire.
-
D.
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.
-
E.
Byzantine official
A Byzantine official is a government functionary of the Eastern Roman (Byzantine) Empire responsible for administering imperial policies, finances, justice, or military affairs within its complex bureaucratic hierarchy.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.