Triple

T21058916
Position Surface form Disambiguated ID Type / Status
Subject Pheres E518799 entity
Predicate hasChild P369 FINISHED
Object Idomene 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: Idomene | Statement: [Pheres, hasChild, Idomene]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Idomene
Context triple: [Pheres, hasChild, Idomene]
  • A. Idomene chosen
    Idomene is a figure in Greek mythology known primarily as the wife of Amythaon and a member of the royal family of Pylos.
  • B. Erasinos
    Erasinos is an ancient river in the region of Attica, Greece, historically associated with the sanctuary and coastal area of Brauron.
  • C. Dagisthaeus
    Dagisthaeus was a 6th-century Byzantine general known for leading imperial forces during the Lazic War against the Sasanian Empire.
  • D. Thagimasadas
    Thagimasadas is a Scythian deity, often interpreted as a god associated with water, horses, and royal power within the ancient Scythian pantheon.
  • E. Sthenelus
    Sthenelus is a figure in Greek mythology, known as a king of Mycenae and a descendant of the hero Perseus.
  • 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_69e0b5053ac48190921529544959e906 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fd8236b481908eebfaeeb2aa63e6 completed April 21, 2026, 4:30 a.m.
Created at: April 16, 2026, 2:37 p.m.