Triple
T18697392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of the Ptolemaic Kingdom of Egypt |
E457156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic royal office |
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 royal office Context triple: [King of the Ptolemaic Kingdom of Egypt, instanceOf, Hellenistic royal office]
-
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 Greek dynasty
An ancient Greek dynasty is a succession of rulers from the same family or lineage who governed a Greek city-state, kingdom, or region over multiple generations in antiquity.
-
D.
Byzantine regency
Byzantine regency refers to the temporary governance arrangement in the Byzantine Empire whereby one or more regents exercised imperial authority on behalf of an underage, absent, or incapacitated emperor.
-
E.
Palmyrene monarch
A Palmyrene monarch is a sovereign ruler of the ancient city-state and later short-lived empire of Palmyra in Roman Syria, exercising political, military, and religious authority over its territories.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.