Triple
T23377045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaeus (son of Seleucus I) |
E593635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Seleucid prince |
C47596
|
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: Seleucid prince Context triple: [Achaeus (son of Seleucus I), instanceOf, Seleucid prince]
-
A.
Seleucid king
A Seleucid king is a Hellenistic monarch who ruled parts of the former Alexandrian empire in the Near East under the Seleucid dynasty, exercising military, administrative, and cultural authority over a diverse, multiethnic realm.
-
B.
regent of the Seleucid Empire
A regent of the Seleucid Empire is an individual who temporarily governed the Hellenistic Seleucid state on behalf of an underage, absent, or otherwise incapacitated king, exercising royal authority without holding the full royal title.
-
C.
Seleucid princess
A Seleucid princess is a royal woman of the Hellenistic Seleucid dynasty, often used as a political pawn through strategic marriages to secure alliances and legitimize territorial control.
-
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.
Maurya prince
A Maurya prince is a royal male heir or member of the ruling family in the ancient Maurya Empire of India, positioned within the imperial hierarchy for governance, military command, and potential succession to the throne.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:33 p.m.