Triple
T19832630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admete |
E476500
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Iphimedon |
—
|
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: Iphimedon | Statement: [Admete, sibling, Iphimedon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iphimedon Context triple: [Admete, sibling, Iphimedon]
-
A.
Iphimedon
chosen
Iphimedon is a figure from Greek mythology known primarily as a royal descendant associated with the city of Tiryns.
-
B.
Iphiclus
Iphiclus is a figure in Greek mythology known primarily as a son of Thestius and thus a member of the royal family of Calydon.
-
C.
Neocles
Neocles was an Athenian of the late 6th century BC, best known as the father of the prominent statesman and general Themistocles.
-
D.
Temenus of Argos
Temenus of Argos is a legendary Heraclid king of Argos in Greek mythology, regarded as an ancestor of the Argead dynasty of Macedon.
-
E.
Demophon
Demophon is a figure in Greek mythology, traditionally known as one of the sons of the Athenian hero Theseus and later a king of Athens.
- 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.