Triple
T8310775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Helios |
E194584
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ptolemaic prince |
C9986
|
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: Ptolemaic prince Context triple: [Alexander Helios, instanceOf, Ptolemaic prince]
-
A.
Ptolemaic ruler
chosen
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.
-
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.
King of Egypt
The King of Egypt is the supreme monarch who holds ultimate political, religious, and military authority over the Egyptian state and its people.
-
D.
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.
-
E.
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.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:54 p.m.