Triple
T5179686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caesarius of Nazianzus |
E116888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Roman Empire official |
C6535
|
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 Empire official Context triple: [Caesarius of Nazianzus, instanceOf, Eastern Roman Empire official]
-
A.
Eastern Roman emperor
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.
Byzantine official
chosen
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.
-
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.
Western Roman emperor
A Western Roman emperor is the sovereign ruler of the western half of the Roman Empire, holding supreme political, military, and religious authority from the late 3rd to the late 5th century CE.
-
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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:45 p.m.