Triple
T13467895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children of Poseidon |
E311549
|
entity |
| Predicate | includes |
P1393
|
FINISHED |
| Object | Tyro's son 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: Tyro's son Pelias | Statement: [Children of Poseidon, includes, Tyro's son Pelias]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tyro's son Pelias Context triple: [Children of Poseidon, includes, Tyro's son 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.
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.
-
D.
King of Phthia
King of Phthia is a mythological Greek royal title associated with the legendary ruler Deucalion, famed as a survivor of a great flood and progenitor of humankind.
-
E.
Athamas
Athamas is a king in Greek mythology, best known for his tragic family saga involving his children and his second wife Ino.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf101a1081909f2aba6da47baacc |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f74629f1408190b54194fe794be39a |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 9, 2026, 9:42 p.m.