Triple

T18595023
Position Surface form Disambiguated ID Type / Status
Subject Periclymenus E454471 entity
Predicate sibling P363 FINISHED
Object Eurybius 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: Eurybius | Statement: [Periclymenus, sibling, Eurybius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eurybius
Context triple: [Periclymenus, sibling, Eurybius]
  • A. Eurybius chosen
    Eurybius is a minor figure in Greek mythology known primarily as one of the sons of Neleus, the king of Pylos.
  • B. Aristodemus of Nysa
    Aristodemus of Nysa was an ancient Greek grammarian and scholar from the city of Nysa, known for his work on language and literary criticism.
  • C. Deimachus
    Deimachus is a relatively obscure figure in Greek mythology known primarily as the father of Neleus, the future king of Pylos.
  • D. Deimachus
    Deimachus is a relatively obscure figure in Greek mythology known primarily as the son of Enarete.
  • E. Aristodemus
    Aristodemus is a figure in Greek mythology, one of the Heracleidae and a descendant of Heracles associated with the legendary return of his lineage to the Peloponnese.
  • 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_69d8d38ae7e081908a98df1251842402 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e545b8d76881909db1539c7150befb completed April 19, 2026, 9:14 p.m.
Created at: April 10, 2026, 11:44 a.m.