Triple
T12604646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titanides |
E300945
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Coeus |
E28029
|
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: Coeus | Statement: [Titanides, sibling, Coeus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Coeus Context triple: [Titanides, sibling, Coeus]
-
A.
Coeus
chosen
Coeus is a Titan from Greek mythology, associated with intelligence and the axis of the heavens, who fought against the Olympian gods.
-
B.
Astraeus
Astraeus is a Titan god in Greek mythology associated with dusk, stars, and astrology.
-
C.
Hippalcimus
Hippalcimus is a minor figure in Greek mythology known primarily as a son of Hippodamia.
-
D.
Adrasteia
Adrasteia is a nymph in Greek mythology associated with nurturing the infant Zeus and sometimes linked with divine retribution and inevitability.
-
E.
Deioneus
Deioneus is a figure in Greek mythology, known primarily as a Thessalian king and the husband of Diomede, and is sometimes identified as the father of the hero Cephalus.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e7f2dc8190a42cab7a0e5ea7f3 |
completed | April 10, 2026, 7:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65ecb09e481909d688f174372dde7 |
completed | May 2, 2026, 8:30 p.m. |
Created at: April 9, 2026, 5:10 p.m.