Triple
T7409012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demonassa |
E170952
|
entity |
| Predicate | hasHusband |
P45367
|
FINISHED |
| Object | Thersander |
E29513
|
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: Thersander | Statement: [Demonassa, hasHusband, Thersander]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thersander Context triple: [Demonassa, hasHusband, Thersander]
-
A.
Thersander
chosen
Thersander is a figure in Greek mythology, known as a descendant of the royal house of Thebes and one of the Epigoni who attacked the city.
-
B.
Talthybius
Talthybius is a herald of the Greek army in Greek mythology, best known from Euripides’ tragedies where he delivers orders and news to captive Trojan women.
-
C.
Azarethes
Azarethes was a prominent Sasanian Persian general noted for his role in the Iberian War against the Eastern Roman (Byzantine) Empire.
-
D.
Timesitheus
Timesitheus was a prominent 3rd-century Roman statesman and praetorian prefect who became a key advisor and father-in-law to Emperor Gordian III.
-
E.
Isander
Isander is a minor figure in Greek mythology known primarily as a son of the hero Bellerophon.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f29acf588190a7c4056bdc4f3ffc |
completed | March 27, 2026, 9:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c82779a1d8819098f136291fa42433 |
completed | March 28, 2026, 7:09 p.m. |
Created at: March 27, 2026, 3:10 p.m.