Triple

T19580435
Position Surface form Disambiguated ID Type / Status
Subject Procne E489972 entity
Predicate spouse P13 FINISHED
Object Tereus 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: Tereus | Statement: [Procne, spouse, Tereus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tereus
Context triple: [Procne, spouse, Tereus]
  • A. Tereus chosen
    Tereus is a figure in Greek mythology, a Thracian king best known for his brutal assault on Philomela and the subsequent transformation of himself and his family into birds.
  • B. Trophonius
    Trophonius is a chthonic figure from Greek religion and myth, renowned for his prophetic oracle and mysterious subterranean shrine.
  • C. Cranaus
    Cranaus is a legendary early king of Athens in Greek mythology, often associated with the city's primeval history before the time of more famous rulers like Erechtheus and Theseus.
  • D. Polydorus of Pherae
    Polydorus of Pherae was a 4th-century BC Thessalian ruler associated with the tyrannical dynasty that controlled the city of Pherae in ancient Greece.
  • E. Ecclemach
    Ecclemach is an alternative name for the Esselen, a Native American people indigenous to the central coast of California.
  • 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_69d8e8dd9374819098e36349b3211663 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6402763b8819099e535979f094f9d completed April 20, 2026, 3:03 p.m.
Created at: April 10, 2026, 1:42 p.m.