Triple
T5354641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lysias |
E102660
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regent of the Seleucid Empire |
C17998
|
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: regent of the Seleucid Empire Context triple: [Lysias, instanceOf, regent of the Seleucid Empire]
-
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.
Hellenistic-era monarch
A Hellenistic-era monarch is a ruler who governed one of the successor kingdoms to Alexander the Great’s empire, blending Greek political and cultural traditions with local customs across a diverse, often expansive territory.
-
C.
Bithynian monarch
A Bithynian monarch is a sovereign ruler of the ancient kingdom of Bithynia in northwestern Anatolia, holding supreme political, military, and ceremonial authority over its territories and people.
-
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.
Ptolemaic ruler
A Ptolemaic ruler is a monarch from the Macedonian Greek dynasty that governed Egypt and surrounding territories from the late 4th century BCE to the Roman conquest, blending Hellenistic and Egyptian political and cultural traditions.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 2:01 p.m.