Triple
T9569362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthemius (praetorian prefect) |
E230874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Roman 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 official Context triple: [Anthemius (praetorian prefect), instanceOf, Eastern Roman official]
-
A.
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.
-
B.
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.
-
C.
Byzantine person
A Byzantine person is an individual who lived in or was culturally associated with the Byzantine Empire, characterized by its Eastern Roman heritage, Orthodox Christian faith, and rich traditions in art, law, and administration.
-
D.
Byzantine jurist
A Byzantine jurist is a legal scholar or judge of the Byzantine Empire who interpreted, applied, and commented on Roman and Byzantine law within the empire’s complex religious and imperial framework.
-
E.
late Roman provincial governor
A late Roman provincial governor was an imperial official responsible for administering a province’s civil government, justice, taxation, and local defense under the increasingly centralized and bureaucratic structures of the later Roman Empire.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:04 p.m.