Triple
T36810373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surena |
E909571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Parthian general |
C65648
|
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: Parthian general Context triple: [Surena, instanceOf, Parthian general]
-
A.
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.
-
B.
Palmyrene general
A Palmyrene general is a high-ranking military commander from the ancient city-state of Palmyra, responsible for leading its armies, planning campaigns, and defending its political and economic interests in the Roman-era Near East.
-
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.
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.
-
E.
Parthian king
A Parthian king is the sovereign ruler of the ancient Parthian Empire, exercising political, military, and religious authority over its territories and peoples.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.