Triple
T6303905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypermnestra |
E141324
|
entity |
| Predicate | grandchild |
P5572
|
FINISHED |
| Object | Acrisius |
E146572
|
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: Acrisius | Statement: [Hypermnestra, grandchild, Acrisius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Acrisius Context triple: [Hypermnestra, grandchild, Acrisius]
-
A.
Acrisius
chosen
Acrisius is a king in Greek mythology, best known as the father of Danaë and the ill-fated grandfather of the hero Perseus.
-
B.
Cranaus
Cranaus is a legendary early king of Athens in Greek mythology, often associated with the city's primeval history before the time of more famous rulers like Erechtheus and Theseus.
-
C.
Cretheus
Cretheus is a figure in Greek mythology, a king of Iolcus and ancestor of the hero Jason.
-
D.
Agrius
Agrius is a figure from Greek mythology known as one of the sons of the sorceress Circe.
-
E.
Dorus
Dorus is a figure in Greek mythology regarded as the eponymous ancestor of the Dorian people.
- 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0645e150881908b49a07914dcbfd8 |
completed | March 22, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e43e085081908546fa120a43bf84 |
completed | March 27, 2026, 1:58 a.m. |
Created at: March 22, 2026, 4:27 p.m.