Triple

T21884023
Position Surface form Disambiguated ID Type / Status
Subject Polyidus E540359 entity
Predicate servedKing P113216 FINISHED
Object Minos 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: Minos | Statement: [Polyidus, servedKing, Minos]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Minos
Context triple: [Polyidus, servedKing, Minos]
  • A. Minos chosen
    Minos is a legendary king of Crete in Greek mythology, famed for commissioning the Labyrinth and serving as a judge of the dead in the underworld.
  • B. Zeus Cretensis
    Zeus Cretensis is a Cretan aspect of the Greek god Zeus, often associated with his birth and early worship on the island of Crete.
  • C. Phoroneus
    Phoroneus is a figure in Greek mythology often regarded as a primordial king of Argos and one of the earliest humans or culture heroes in the region.
  • D. Hekademos
    Hekademos (or Hecademus) was an Athenian hero or local figure whose grove outside Athens became the site of Plato’s Academy, giving the school its name.
  • E. Deinomenes
    Deinomenes was an ancient Greek figure known primarily as the father of Gelon, the powerful tyrant of Gela and Syracuse in the early 5th century BCE.
  • 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_69e0c479a98081908ce333853fdd4348 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f118e9d3508190aadcfcdac0376387 completed April 28, 2026, 8:30 p.m.
Created at: April 16, 2026, 7:05 p.m.