Triple
T32209779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegidius |
E822766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late Roman military commander |
C10598
|
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 military commander Context triple: [Aegidius, instanceOf, late Roman military commander]
-
A.
Roman military commander
chosen
A Roman military commander is a high-ranking officer responsible for leading legions, planning and executing campaigns, maintaining discipline, and securing Rome’s political and territorial interests through organized warfare.
-
B.
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.
-
C.
Isaurian general
An Isaurian general is a high-ranking military commander originating from the rugged Isauria region of Asia Minor, often serving in the Roman or Byzantine armies and known for their fierce, hardy reputation.
-
D.
Ostrogothic general
An Ostrogothic general is a high-ranking military commander of the Ostrogothic Kingdom, responsible for leading Gothic armies, planning campaigns, and defending or expanding the realm in the post-Roman world.
-
E.
Roman consul
A Roman consul was one of the two annually elected chief magistrates of the Roman Republic (and later an important office in the Empire), holding supreme civil and military authority and presiding over the Senate and assemblies.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:37 a.m.