Triple
T37783468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleomenes III of Sparta |
E941889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic-period ruler |
C12843
|
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-period ruler Context triple: [Cleomenes III of Sparta, instanceOf, Hellenistic-period ruler]
-
A.
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.
-
B.
ancient Greek ruler
chosen
An ancient Greek ruler is a sovereign leader who governed a Greek city-state or kingdom, wielding political, military, and often religious authority within the context of classical Hellenic civilization.
-
C.
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.
-
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.
2nd-century BCE ruler
A 2nd-century BCE ruler is a sovereign who governed a state or empire between 200 and 101 BCE, navigating the complex political, military, and cultural dynamics of the Hellenistic, Roman Republican, and other contemporaneous civilizations.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.