Triple
T31420014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zabdas |
E801503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Palmyrene general |
C60063
|
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: Palmyrene general Context triple: [Zabdas, instanceOf, Palmyrene general]
-
A.
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.
-
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.
Palmyrene ruler
A Palmyrene ruler is a sovereign or governing authority who held political power over the ancient city-state of Palmyra and its territories, particularly during the Roman and early Byzantine periods.
-
D.
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.
-
E.
Palmyrene prince
A Palmyrene prince is a male member of the royal or ruling elite of the ancient city-state of Palmyra in Roman Syria, often involved in governance, military leadership, and regional diplomacy.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 8:47 p.m.