Triple
T20011971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermia |
E494610
|
entity |
| Predicate | hasFather |
P1908
|
FINISHED |
| Object | Egeus |
—
|
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: Egeus | Statement: [Hermia, hasFather, Egeus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Egeus Context triple: [Hermia, hasFather, Egeus]
-
A.
Egeus
chosen
Egeus is a strict Athenian nobleman and father of Hermia in Shakespeare's comedy "A Midsummer Night's Dream," whose insistence on controlling his daughter's marriage helps drive the play's central conflict.
-
B.
Mnesilochus
Mnesilochus is a comic character in Aristophanes’ play "Thesmophoriazusae," known for disguising himself as a woman to infiltrate a secret women’s festival.
-
C.
Antiphus
Antiphus is a minor figure in Greek mythology, known primarily as one of the many sons of King Priam of Troy who perished in the Trojan War.
-
D.
Antiphus
Antiphus is a figure in Greek mythology, known as a son of Alcimede and often associated with heroic lineages linked to the Argonauts.
-
E.
Theseus
Theseus is a legendary hero of Greek mythology best known for slaying the Minotaur and serving as the mythical king and unifier 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623773d88190826616a02d3c3e69 |
completed | April 20, 2026, 5:28 p.m. |
Created at: April 11, 2026, 3:34 p.m.