Triple
T4922187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telephus |
E110490
|
entity |
| Predicate | parentOf |
P120
|
FINISHED |
| Object | Eurypylus of Mysia |
E352355
|
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: Eurypylus of Mysia | Statement: [Telephus, parentOf, Eurypylus of Mysia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eurypylus of Mysia Context triple: [Telephus, parentOf, Eurypylus of Mysia]
-
A.
Eurypylus
chosen
Eurypylus is a figure in Greek mythology, known in various traditions as a son of notable heroes and a participant in legendary wars such as the Trojan War.
-
B.
Neocles
Neocles was an Athenian of the late 6th century BC, best known as the father of the prominent statesman and general Themistocles.
-
C.
Euphorbus
Euphorbus is a Trojan warrior in Greek mythology, noted for wounding Patroclus during the Trojan War before the latter was finally slain.
-
D.
Antilochus
Antilochus is a figure in Greek mythology, a son of Nestor renowned for his bravery and close friendship with Achilles during the Trojan War.
-
E.
Tlepolemus
Tlepolemus is a figure in Greek mythology, known as a son of Heracles who became a leader of Rhodian forces in the Trojan War.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be77a41ca08190a8fbfa405b15d68c |
completed | March 21, 2026, 10:49 a.m. |
Created at: March 20, 2026, 1:30 p.m.