Triple

T20950205
Position Surface form Disambiguated ID Type / Status
Subject Polymestor E515956 entity
Predicate betrayed P25013 FINISHED
Object Polydorus 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: Polydorus | Statement: [Polymestor, betrayed, Polydorus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Polydorus
Context triple: [Polymestor, betrayed, Polydorus]
  • A. Polydorus
    Polydorus is a figure in Greek mythology, traditionally known as a son of Cadmus and Harmonia and thus a Theban prince.
  • B. Polydorus chosen
    Polydorus is a figure in Greek mythology, traditionally known as the youngest son of King Priam of Troy whose tragic death is recounted in various ancient sources.
  • C. Polydorus of Pherae
    Polydorus of Pherae was a 4th-century BC Thessalian ruler associated with the tyrannical dynasty that controlled the city of Pherae in ancient Greece.
  • D. Polymnestor
    Polymnestor is a figure in Greek mythology, a Thracian king best known for murdering the young Polydorus for gold and later being blinded and having his sons killed in revenge by Hecuba.
  • E. Deiphontes
    Deiphontes is a figure in Greek mythology known as a Heraclid prince and son-in-law of Temenus, associated with the royal lineage of Argos.
  • 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_69e0b4fcd678819087a304291f14330a completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fadd3bd88190a0d1fdea9d300fc0 completed April 21, 2026, 4:19 a.m.
Created at: April 16, 2026, 1:23 p.m.