Triple
T4564170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyro |
E121868
|
entity |
| Predicate | motherOf |
P120
|
FINISHED |
| Object | Pelias |
E234813
|
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: Pelias | Statement: [Tyro, motherOf, Pelias]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pelias Context triple: [Tyro, motherOf, Pelias]
-
A.
Pelias
chosen
Pelias is a figure in Greek mythology, best known as the usurping king of Iolcus who sent Jason on the quest for the Golden Fleece.
-
B.
Aeëtes
Aeëtes is a king in Greek mythology, best known as the ruler of Colchis and keeper of the Golden Fleece.
-
C.
Admetus
Admetus is a king in Greek mythology best known for being granted the chance to escape death through another’s sacrifice, a role famously linked with his devoted wife Alcestis.
-
D.
Peleus
Peleus is a hero in Greek mythology, a king of Phthia and husband of the sea nymph Thetis, best known as the father of Achilles.
-
E.
Polydectes
Polydectes is a king in Greek mythology best known for sending Perseus on the quest to slay Medusa in an attempt to get rid of him.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589b439c81908da9d19433310bcd |
completed | March 20, 2026, 2:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdc5a8ea5481908a652290e9df911f |
completed | March 20, 2026, 10:09 p.m. |
Created at: March 20, 2026, 1:09 p.m.