Triple
T36019890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simeon Uroš |
E1041953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine-style 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-style emperor Context triple: [Simeon Uroš, instanceOf, Byzantine-style emperor]
-
A.
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.
-
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.
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.
-
D.
Eastern Orthodox monarch
An Eastern Orthodox monarch is a sovereign ruler whose authority and legitimacy are closely tied to the traditions, theology, and ecclesiastical structures of the Eastern Orthodox Church, often serving as both a political leader and a protector of the faith.
-
E.
Byzantine imperial dynasty
A Byzantine imperial dynasty is a succession of related rulers who governed the Eastern Roman (Byzantine) Empire, shaping its political, religious, and cultural life over multiple generations.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.