Triple
T19832615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admete |
E476500
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Eurystheus |
—
|
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: Eurystheus | Statement: [Admete, father, Eurystheus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eurystheus Context triple: [Admete, father, Eurystheus]
-
A.
Eurystheus
chosen
Eurystheus is the mythological king of Tiryns and Mycenae in Greek mythology who imposed the Twelve Labors upon Heracles.
-
B.
Aeëtes
Aeëtes is a king in Greek mythology, best known as the ruler of Colchis and keeper of the Golden Fleece.
-
C.
Aeacus
Aeacus is a just and pious king from Greek mythology who ruled the island of Aegina and later became one of the three judges of the dead in the underworld.
-
D.
Pelops
Pelops is a figure in Greek mythology, a son of Tantalus whose descendants formed a powerful and ill-fated royal lineage marked by curses and tragic events.
-
E.
Polydectes
Polydectes is a king in Greek mythology best known for sending Perseus on the quest to slay Medusa in an attempt to get rid of him.
- 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_69e656cf7e488190b4be28b5e7b363bf |
completed | April 20, 2026, 4:39 p.m. |
Created at: April 10, 2026, 1:50 p.m.