Triple
T5176001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deianira |
E116798
|
entity |
| Predicate | alternateName |
P39
|
FINISHED |
| Object | Deianeira |
E116798
|
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: Deianeira | Statement: [Deianira, alternateName, Deianeira]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Deianeira Context triple: [Deianira, alternateName, Deianeira]
-
A.
Deianira
chosen
Deianira is a figure in Greek mythology best known as the second wife of the hero Heracles and for inadvertently causing his death through the poisoned tunic.
-
B.
Creusa
Creusa is a figure in Greek mythology, often depicted as an Athenian princess and mother of Ion in Euripides’ tragedy.
-
C.
Creusa
Creusa is a figure in Greek mythology, best known as a Trojan princess and the wife of the hero Aeneas.
-
D.
Oenone
Oenone is a nymph from Greek mythology, known as the first wife of Paris of Troy and a tragic figure in the events surrounding the Trojan War.
-
E.
Clorinda
Clorinda is a border city in northeastern Argentina’s Formosa Province, located opposite Asunción, Paraguay, and serving as an important regional commercial and transport hub.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd797349008190b87ad9d0d3eb667f |
completed | March 20, 2026, 4:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bed94e269481908118fd1af1fc6a44 |
completed | March 21, 2026, 5:45 p.m. |
Created at: March 20, 2026, 1:45 p.m.