Triple
T15693322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcestis |
E380389
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Admetus |
E380385
|
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: Admetus | Statement: [Alcestis, spouse, Admetus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Admetus Context triple: [Alcestis, spouse, Admetus]
-
A.
Admetus
chosen
Admetus is a king in Greek mythology best known for being granted the chance to escape death through another’s sacrifice, a role famously linked with his devoted wife Alcestis.
-
B.
Menoeceus
Menoeceus was an associate and student of the ancient Greek philosopher Epicurus, best known as the addressee of Epicurus’ ethical treatise commonly called the "Letter to Menoeceus."
-
C.
Adrastus
Adrastus is a legendary king of Argos in Greek mythology, best known as the leader of the Seven Against Thebes.
-
D.
Deiphobus
Deiphobus is a prince of Troy in Greek mythology, known as one of Priam's sons and a prominent warrior during the Trojan War.
-
E.
Pheneus
Pheneus was an ancient Arcadian city in the northeastern Peloponnese, known from Greek mythology and classical geography.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f4f5a888190bd3681bcb9bbc02f |
completed | April 16, 2026, 2:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6eed9a8c8190a57ffce61a27ec17 |
completed | May 9, 2026, 5:29 p.m. |
Created at: April 10, 2026, 4:44 a.m.