Triple
T15444981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiberius (son of Constans II) |
E369999
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine co-emperor |
C11929
|
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 co-emperor Context triple: [Tiberius (son of Constans II), instanceOf, Byzantine co-emperor]
-
A.
regent of the Eastern Roman Empire
A regent of the Eastern Roman Empire is an appointed or self-declared authority who governs the empire on behalf of a reigning but underage, absent, incapacitated, or otherwise unable emperor, wielding imperial power without holding the imperial title.
-
B.
Latin Emperor of Constantinople
The Latin Emperor of Constantinople was the Western European ruler installed after the Fourth Crusade (1204–1261) to govern the Latin Empire in place of the Byzantine emperors.
-
C.
Eastern Roman emperor
chosen
An Eastern Roman emperor is the sovereign ruler of the eastern portion of the Roman Empire, later known as the Byzantine Empire, wielding supreme political, military, and religious authority.
-
D.
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.
-
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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
Created at: April 10, 2026, 3:21 a.m.