Triple
T22199612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurythemis |
E548640
|
entity |
| Predicate | hasRelative |
P367
|
FINISHED |
| Object | Evippus |
—
|
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: Evippus | Statement: [Eurythemis, hasRelative, Evippus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Evippus Context triple: [Eurythemis, hasRelative, Evippus]
-
A.
Evippus
chosen
Evippus is a minor figure in Greek mythology known primarily as one of the sons of King Thestius and the brother of Althaea.
-
B.
Orgilus
Orgilus is a central tragic figure in John Ford’s Jacobean revenge play "The Broken Heart," known for his stoic suffering and complex, restrained passion.
-
C.
Vopiscus
Vopiscus is a rare and archaic Latin praenomen (given name) occasionally used in ancient Roman families such as the gens Julia.
-
D.
Aethlius
Aethlius is a figure in Greek mythology, often regarded as an early king of Elis and associated with the lineage of heroic rulers.
-
E.
Lycopeus
Lycopeus is a minor figure in Greek mythology known primarily as a son of the Calydonian king Oeneus.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aea51d48190a570cd36c106ab78 |
completed | April 28, 2026, 9:47 p.m. |
Created at: April 16, 2026, 8:36 p.m.