Triple
T21062008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iphiclus |
E518871
|
entity |
| Predicate | hasNameInGreek |
P3659
|
FINISHED |
| Object | Ἴφικλος |
—
|
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: Ἴφικλος | Statement: [Iphiclus, hasNameInGreek, Ἴφικλος]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ἴφικλος Context triple: [Iphiclus, hasNameInGreek, Ἴφικλος]
-
A.
Idomeneus
Idomeneus is a legendary Cretan king and warrior in Greek mythology, renowned as one of the prominent Greek leaders and fighters in the Trojan War.
-
B.
Tlepolemus
Tlepolemus is a figure in Greek mythology, known as a son of Heracles who became a leader of Rhodian forces in the Trojan War.
-
C.
Iphiclus
chosen
Iphiclus is a figure in Greek mythology known primarily as a son of Thestius and thus a member of the royal family of Calydon.
-
D.
Neocles
Neocles was an Athenian of the late 6th century BC, best known as the father of the prominent statesman and general Themistocles.
-
E.
Ἀϊδωνεύς (Aidoneus)
Ἀϊδωνεύς (Aidoneus) is an epithet and alternate name for Hades, the ancient Greek god who rules the underworld and the realm of the dead.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb064a48190b892b78e27e8d0fa |
completed | April 21, 2026, 4:36 a.m. |
Created at: April 16, 2026, 2:38 p.m.