Triple
T28773973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspar |
E726484
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Roman general |
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: Eastern Roman general Context triple: [Aspar, instanceOf, Eastern Roman general]
-
A.
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.
-
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.
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.
-
D.
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.
-
E.
Assyrian general
An Assyrian general is a high-ranking military commander in the ancient Assyrian Empire responsible for planning campaigns, leading armies in battle, and enforcing the king’s authority through warfare and conquest.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:17 a.m.