Triple
T19832043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iphicles |
E476485
|
entity |
| Predicate | hasChild |
P369
|
FINISHED |
| Object | Iolaus |
—
|
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: Iolaus | Statement: [Iphicles, hasChild, Iolaus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iolaus Context triple: [Iphicles, hasChild, Iolaus]
-
A.
Iolaus
chosen
Iolaus is a hero in Greek mythology best known as the loyal nephew and charioteer of Heracles, who aided him in several of his labors, especially the slaying of the Hydra.
-
B.
Telophorus
Telophorus is a genus of bushshrikes, medium-sized insectivorous passerine birds native to sub-Saharan Africa.
-
C.
Thessalus
Thessalus is a figure from Greek mythology, traditionally known as a son of the hero Jason and Alcimede.
-
D.
Aphareus
Aphareus is a figure in Greek mythology, traditionally known as a Messenian king and son of the hero Perieres and Gorgophone.
-
E.
Epilaus
Epilaus is a minor figure in Greek mythology known primarily as one of the sons of Neleus, the king of Pylos.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656ce68b48190aa25b29d0b6ea021 |
completed | April 20, 2026, 4:39 p.m. |
Created at: April 10, 2026, 1:50 p.m.