Triple
T4896703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ismene |
E109699
|
entity |
| Predicate | grandfather |
P979
|
FINISHED |
| Object | Laius |
E111289
|
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: Laius | Statement: [Ismene, grandfather, Laius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Laius Context triple: [Ismene, grandfather, Laius]
-
A.
Laius
chosen
Laius is a mythological king of Thebes in Greek tragedy, best known for the prophecy that his son would kill him and marry his wife, setting the stage for the story of Oedipus.
-
B.
Oedipus
Oedipus is a tragic hero in Greek mythology best known for unwittingly killing his father and marrying his mother, a fate he was prophesied to fulfill.
-
C.
Orestheus
Orestheus is a minor figure in Greek mythology known primarily as a son of the flood survivor and progenitor of humankind, Deucalion.
-
D.
Jocasta
Jocasta is a tragic figure in Greek mythology and Sophocles' play "Oedipus Rex," known as both the wife and unwitting mother of Oedipus, whose discovery of their incestuous relationship leads to catastrophe.
-
E.
Creon
Creon is a mythological king of Thebes in Greek tragedy, best known for his roles in the stories of Oedipus and Antigone.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e2923a081909bd592880b6f399b |
completed | March 20, 2026, 3:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6fc997548190bb340193475065ee |
completed | March 21, 2026, 10:15 a.m. |
Created at: March 20, 2026, 1:28 p.m.