Triple
T11306322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Helena |
E267722
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Empress of the Roman Empire |
C9681
|
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: Empress of the Roman Empire Context triple: [Saint Helena, instanceOf, Empress of the Roman Empire]
-
A.
Roman empress
chosen
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.
-
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.
imperial prince of Rome
An imperial prince of Rome is a male member of the ruling emperor’s family, often positioned as a potential heir and endowed with high status, privileges, and political influence within the Roman imperial hierarchy.
-
D.
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.
-
E.
regent of the Western Roman Empire
A regent of the Western Roman Empire was an individual who governed the empire on behalf of an underage, absent, or otherwise incapacitated Western Roman emperor, exercising imperial authority without holding the imperial title.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.