Triple

T22199614
Position Surface form Disambiguated ID Type / Status
Subject Eurythemis E548640 entity
Predicate hasRelative P367 FINISHED
Object Eurypylus 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: Eurypylus | Statement: [Eurythemis, hasRelative, Eurypylus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eurypylus
Context triple: [Eurythemis, hasRelative, Eurypylus]
  • 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. 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.
  • C. Lyrnessus
    Lyrnessus is an ancient city in Asia Minor known from Greek mythology as the captured home of Briseis during the Trojan War.
  • D. Ἀϊδωνεύς (Aidoneus)
    Ἀϊδωνεύς (Aidoneus) is an epithet and alternate name for Hades, the ancient Greek god who rules the underworld and the realm of the dead.
  • E. Tementhes
    Tementhes is an alternative name for Tantamani, a Kushite pharaoh of Egypt’s 25th Dynasty known for his attempts to restore Nubian rule over Egypt.
  • 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_69e11e3ecc7c8190b5f94cd8f42e9d37 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12aea51d48190a570cd36c106ab78 completed April 28, 2026, 9:47 p.m.
Created at: April 16, 2026, 8:36 p.m.