Triple
T9702816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argo |
E234819
|
entity |
| Predicate | hasFigureFromMyth |
P86125
|
FINISHED |
| Object | Tiphys |
E638017
|
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: Tiphys | Statement: [Argo, hasFigureFromMyth, Tiphys]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tiphys Context triple: [Argo, hasFigureFromMyth, Tiphys]
-
A.
Tiphys
chosen
Tiphys is the skilled helmsman of the Argo in Greek mythology, responsible for steering Jason and the Argonauts on their quest for the Golden Fleece.
-
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.
Aethlius
Aethlius is a figure in Greek mythology, often regarded as an early king of Elis and associated with the lineage of heroic rulers.
-
D.
Catreus
Catreus is a figure in Greek mythology, a son of King Minos of Crete whose tragic fate is tied to a prophecy that he would be killed by one of his own children.
-
E.
Phaeo
Phaeo is a lesser-known figure in Greek mythology, identified as a daughter of the Titan Atlas.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d7283188190bd50e18f643ad0d3 |
completed | April 1, 2026, 10:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19132687c8190baf3a60af1b789a8 |
completed | April 4, 2026, 10:31 p.m. |
Created at: March 30, 2026, 8:18 p.m.