Triple

T19988980
Position Surface form Disambiguated ID Type / Status
Subject Poseidon E494008 entity
Predicate opponent P437 FINISHED
Object Polybotes 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: Polybotes | Statement: [Poseidon, opponent, Polybotes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Polybotes
Context triple: [Poseidon, opponent, Polybotes]
  • A. Polybotes chosen
    Polybotes is a giant from Greek mythology best known for battling the sea god Poseidon during the Gigantomachy.
  • B. Ancaeus
    Ancaeus is a figure in Greek mythology, often depicted as a bold but ill-fated hero and Argonaut who met his death during the legendary Calydonian Boar Hunt.
  • C. Eurytion
    Eurytion is a herdsman in Greek mythology best known for guarding the cattle of the three-bodied giant Geryon, whom Heracles killed during his tenth labor.
  • D. Dagisthaeus
    Dagisthaeus was a 6th-century Byzantine general known for leading imperial forces during the Lazic War against the Sasanian Empire.
  • E. Aleus
    Aleus is a figure in Greek mythology, a king of Tegea in Arcadia and a descendant of the god Arcas.
  • 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65fddfee081909aa8cd6e279b2a7a completed April 20, 2026, 5:18 p.m.
Created at: April 11, 2026, 3:30 p.m.