Triple
T35849473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megabyzus |
E1036309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Achaemenid general |
C33979
|
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: Achaemenid general Context triple: [Megabyzus, instanceOf, Achaemenid general]
-
A.
Persian military commander
chosen
A Persian military commander is a high-ranking leader responsible for planning, directing, and overseeing the armed forces of Persia in warfare and defense operations.
-
B.
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.
-
C.
Seleucid general
A Seleucid general is a high-ranking military commander serving the Hellenistic Seleucid Empire, responsible for leading armies, managing campaigns, and maintaining imperial control over diverse and often contested territories.
-
D.
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.
-
E.
Achaemenid noble
An Achaemenid noble is a high-ranking member of the Persian aristocracy who held land, military command, and administrative authority under the Achaemenid Empire, often serving as a close supporter and regional representative of the Great King.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.