Triple
T11844183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbogast |
E281728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late Roman Empire person |
C16221
|
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: late Roman Empire person Context triple: [Arbogast, instanceOf, late Roman Empire person]
-
A.
4th-century Roman person
A 4th-century Roman person is an individual who lived within the Roman Empire during the 300s CE, shaped by the era’s political transformations, military conflicts, and the growing influence of Christianity.
-
B.
Roman official
A Roman official is a government functionary of ancient Rome responsible for administering laws, finances, justice, or public works within the Republic or Empire.
-
C.
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.
-
D.
late Roman provincial governor
chosen
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.
-
E.
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.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.