Triple
T2177567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantius II |
E48565
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 4th-century Roman emperor |
C7879
|
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: 4th-century Roman emperor Context triple: [Constantius II, instanceOf, 4th-century Roman emperor]
-
A.
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.
-
B.
4th-century Christian bishop
A 4th-century Christian bishop was a high-ranking church leader responsible for overseeing a Christian community, defending orthodoxy amid theological controversies, and guiding the church through the transition from persecution to imperial favor.
-
C.
Herodian dynasty member
A Herodian dynasty member is an individual belonging to the ruling family established by Herod the Great, which governed Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
-
D.
deified Roman
A deified Roman is a mortal individual from ancient Rome who, after death, was officially elevated to divine status and worshipped as a god within the Roman religious and political system.
-
E.
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.
- F. None of above. chosen
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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:45 p.m.