Triple
T17653897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oenopion |
E429564
|
entity |
| Predicate | hasSons |
P60575
|
FINISHED |
| Object | Talus (son of Oenopion) |
—
|
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: Talus (son of Oenopion) | Statement: [Oenopion, hasSons, Talus (son of Oenopion)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Talus (son of Oenopion) Context triple: [Oenopion, hasSons, Talus (son of Oenopion)]
-
A.
Talus (son of Oenopion)
chosen
Talus, in Greek mythology, is a son of Oenopion, the king of Chios, and a lesser-known member of the royal family associated with the island’s early mythic rulers.
-
B.
Temenus of Argos
Temenus of Argos is a legendary Heraclid king of Argos in Greek mythology, regarded as an ancestor of the Argead dynasty of Macedon.
-
C.
Hippalcimus
Hippalcimus is a minor figure in Greek mythology known primarily as a son of Hippodamia.
-
D.
Heleus
Heleus is a figure in Greek mythology known as a son of Perseus and Andromeda.
-
E.
Iphiclus
Iphiclus is a figure in Greek mythology known primarily as a son of Thestius and thus a member of the royal family of Calydon.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e3ed8b08190a00efdad9740bf6f |
completed | April 19, 2026, 5:55 a.m. |
Created at: April 10, 2026, 6:05 a.m.