Triple
T4886208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphitryon |
E109444
|
entity |
| Predicate | fatherOf |
P120
|
FINISHED |
| Object | Iphicles |
E121509
|
NE FINISHED |
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: Iphicles | Statement: [Amphitryon, fatherOf, Iphicles]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iphicles Context triple: [Amphitryon, fatherOf, Iphicles]
-
A.
Iphicles
chosen
Iphicles is a figure in Greek mythology best known as the mortal half-brother of the hero Heracles.
-
B.
Enipeus
Enipeus is a river god in Greek mythology, personifying a famous river of Thessaly and known for being the object of Tyro’s love.
-
C.
Iasius
Iasius is a figure in Greek mythology, often identified with Iasion, who is associated with Demeter and sometimes regarded as a founder-hero linked to agriculture and mystery rites.
-
D.
Amnisos
Amnisos is an ancient Minoan harbor site on the north coast of Crete, known from Greek myth and archaeology as a cult center associated with the goddess Eileithyia.
-
E.
Sthenelus
Sthenelus is a figure in Greek mythology, known as a king of Mycenae and a descendant of the hero Perseus.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be680fd1508190bc01caeea8f56f84 |
completed | March 21, 2026, 9:42 a.m. |
Created at: March 20, 2026, 1:28 p.m.