Triple

T7449077
Position Surface form Disambiguated ID Type / Status
Subject Periphetes E171959 entity
Predicate hasAlias P455 FINISHED
Object Korynetes E666293 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: Korynetes | Statement: [Periphetes, hasAlias, Korynetes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Korynetes
Context triple: [Periphetes, hasAlias, Korynetes]
  • A. Corynetes chosen
    Corynetes is an epithet of the mythological bandit Periphetes, a club-wielding villain slain by the hero Theseus in Greek mythology.
  • B. Ariphron
    Ariphron was an Athenian statesman of the 5th century BCE, known primarily as the elder brother of the famous orator Pericles.
  • C. Orthagoras
    Orthagoras was an early tyrant of the ancient Greek city-state of Sicyon, traditionally regarded as the founder of a ruling dynasty there in the 7th century BCE.
  • D. Apheidas
    Apheidas is a minor figure in Greek mythology known primarily as a child of the Muse Erato.
  • E. Ctesippus
    Ctesippus is a figure in Greek mythology known as the son of Hyllus and thus a descendant of the hero Heracles.
  • 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_69c68a65402881908f7869368eb746fb completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f389ddd48190a4b8753c67220c4f completed March 27, 2026, 9:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69c83c57e1d0819081562638236debce completed March 28, 2026, 8:38 p.m.
Created at: March 27, 2026, 3:14 p.m.