Triple

T23317938
Position Surface form Disambiguated ID Type / Status
Subject Procrustes E590760 entity
Predicate alsoKnownAs P39 FINISHED
Object Polypemon 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: Polypemon | Statement: [Procrustes, alsoKnownAs, Polypemon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Polypemon
Context triple: [Procrustes, alsoKnownAs, Polypemon]
  • A. Polypemon chosen
    Polypemon is a figure in Greek mythology known primarily as the father of the notorious bandit Sinis.
  • B. Ambrysus
    Ambrysus was an ancient Greek city in the region of Phocis, known for its strategic location and role in classical Greek history.
  • C. Blepyrus
    Blepyrus is a comic character in Aristophanes’ play *Ecclesiazusae*, typically portrayed as a bemused Athenian husband caught up in the play’s satirical treatment of gender and political reform.
  • D. Polypoetes
    Polypoetes is a figure in Greek mythology, known as a leader of the Lapiths who fought in the Trojan War and at the battle against the Centaurs.
  • E. Gorgophonus
    Gorgophonus is a minor figure in Greek mythology, known primarily as one of the sons of King Electryon of Mycenae and thus a member of the royal lineage connected to Heracles.
  • 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_69e25d1d32188190948eb76909d1dcc3 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f197828c408190ae071624e40de4cc completed April 29, 2026, 5:30 a.m.
Created at: April 17, 2026, 5:07 p.m.