Triple

T20342288
Position Surface form Disambiguated ID Type / Status
Subject Licymnius E495768 entity
Predicate killedBy P4646 FINISHED
Object Tlepolemus 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: Tlepolemus | Statement: [Licymnius, killedBy, Tlepolemus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tlepolemus
Context triple: [Licymnius, killedBy, Tlepolemus]
  • A. Tlepolemus chosen
    Tlepolemus is a figure in Greek mythology, known as a son of Heracles who became a leader of Rhodian forces in 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. Aristion
    Aristion was an early Christian figure, likely a disciple or associate of the apostles, known from Papias’s traditions as a bearer of oral teachings about Jesus.
  • D. Philocles
    Philocles was an Athenian naval commander during the late Peloponnesian War, noted for his role in the decisive defeat at Aegospotami.
  • E. Thrasymedes
    Thrasymedes is a figure in Greek mythology, a son of Nestor who fought as a warrior in the Trojan War.
  • 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_69e0b4a3320881909495ae8bc30bc2dc completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67835f6e881908834dda06cf66c50 completed April 20, 2026, 7:02 p.m.
Created at: April 16, 2026, 11:24 a.m.