Triple

T7324746
Position Surface form Disambiguated ID Type / Status
Subject Procrustes E168842 entity
Predicate epithet P743 FINISHED
Object Polypemon E657687 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: Polypemon | Statement: [Procrustes, epithet, Polypemon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Polypemon
Context triple: [Procrustes, epithet, 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. 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.
  • D. Smargadus
    Smargadus was the exarch of Ravenna who commissioned the Column of Phocas in the Roman Forum in the early 7th century.
  • E. Phylacus
    Phylacus is a figure from Greek mythology known as a leader of the Magnetes, a Thessalian people mentioned in epic tradition.
  • 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_69c68a54cacc81908e3b773441f19566 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f04993408190b73fb46d83a632d5 completed March 27, 2026, 9:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7fa7bfe248190a5def09d6941e114 completed March 28, 2026, 3:57 p.m.
Created at: March 27, 2026, 3:03 p.m.