Triple
T18444119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hieron I of Syracuse |
E450611
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Deinomenes |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Deinomenes | Statement: [Hieron I of Syracuse, father, Deinomenes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Deinomenes Context triple: [Hieron I of Syracuse, father, Deinomenes]
-
A.
Deinomenes
chosen
Deinomenes was an ancient Greek figure known primarily as the father of Gelon, the powerful tyrant of Gela and Syracuse in the early 5th century BCE.
-
B.
Heleus
Heleus is a figure in Greek mythology known as a son of Perseus and Andromeda.
-
C.
Amphictyon
Amphictyon is a figure in Greek mythology, traditionally regarded as an early king of Athens and associated with the legendary Amphictyonic League.
-
D.
Dagisthaeus
Dagisthaeus was a 6th-century Byzantine general known for leading imperial forces during the Lazic War against the Sasanian Empire.
-
E.
Pheneus
Pheneus was an ancient Arcadian city in the northeastern Peloponnese, known from Greek mythology and classical geography.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c142abc8190b4f6f938acdc413d |
completed | April 19, 2026, 6:16 p.m. |
Created at: April 10, 2026, 11:30 a.m.