Triple
T37261007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyzalus |
E924257
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Deinomenid dynasty member |
C12844
|
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: Deinomenid dynasty member Context triple: [Polyzalus, instanceOf, Deinomenid dynasty member]
-
A.
member of the Deinomenid dynasty
chosen
A member of the Deinomenid dynasty is an individual belonging to the ruling family that controlled Syracuse and parts of Sicily in the early 5th century BCE, originating from the tyrant Gelon and his relatives.
-
B.
Attalid dynasty member
An Attalid dynasty member is an individual belonging to the Hellenistic royal family that ruled the kingdom of Pergamon in Asia Minor from the early 3rd to the mid-2nd century BCE.
-
C.
Ezzonid dynasty member
An Ezzonid dynasty member is an individual belonging to the influential noble family that held significant territorial and political power in the Rhineland region of the Holy Roman Empire during the 10th and 11th centuries.
-
D.
Spartocid dynasty member
A Spartocid dynasty member is an individual belonging to the ruling family of the Bosporan Kingdom, which governed the Cimmerian Bosporus region from the 5th to the 2nd century BCE.
-
E.
member of the Antipatrid dynasty
A member of the Antipatrid dynasty is an individual belonging to the Macedonian royal house founded by Antipater, which briefly ruled Macedonia in the late 4th century BCE following the fragmentation of Alexander the Great’s empire.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.