Triple
T9445162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptolemy Philadelphus |
E227745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic prince |
C15338
|
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: Hellenistic prince Context triple: [Ptolemy Philadelphus, instanceOf, Hellenistic prince]
-
A.
Hellenistic-era monarch
chosen
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.
-
B.
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.
-
C.
ancient Macedonian nobleman
An ancient Macedonian nobleman is a high-ranking member of Macedonian aristocracy who held land, military command, and political influence within the kingdom’s hierarchical social and governmental structure.
-
D.
Cretan prince
A Cretan prince is a royal male heir or ruler from the ancient island of Crete, often associated with Minoan culture, mythic lineage, and Mediterranean political power.
-
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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
Created at: March 30, 2026, 7:51 p.m.