Triple
T23067677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euphemia |
E575096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Roman empress consort |
C9962
|
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: Eastern Roman empress consort Context triple: [Euphemia, instanceOf, Eastern Roman empress consort]
-
A.
Byzantine empress consort
chosen
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.
-
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.
Roman empress
A Roman empress is the wife or female counterpart of a Roman emperor, often wielding significant political, social, and cultural influence within the imperial court and broader empire.
-
D.
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.
-
E.
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.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:55 p.m.