Triple

T11366263
Position Surface form Disambiguated ID Type / Status
Subject Ladon E269211 entity
Predicate hasParent P120 FINISHED
Object Phorcys E249784 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: Phorcys | Statement: [Ladon, hasParent, Phorcys]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Phorcys
Context triple: [Ladon, hasParent, Phorcys]
  • A. Phorcys chosen
    Phorcys is a primordial sea deity in Greek mythology, often depicted as an ancient sea god associated with various monstrous offspring.
  • B. Glaucus
    Glaucus is a sea-god from Greek mythology, often depicted as a transformed fisherman endowed with prophetic powers.
  • C. Glaucus
    Glaucus is a figure in Greek mythology, known as a Cretan prince and son of King Minos and Pasiphaë.
  • D. Glaucus
    Glaucus is a character associated with the darkly comedic, countercultural world of the film "Harold and Maude," reflecting its themes of unconventional relationships and existential rebellion.
  • E. Alcyoneus
    Alcyoneus is a formidable giant in Greek mythology, best known as one of the chief opponents of the Olympian gods during the Gigantomachy.
  • 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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea88558c8190aa18881af51a7b96 completed April 9, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e556718fc481908543ed4bc5fe3d6e completed April 19, 2026, 10:25 p.m.
Created at: April 8, 2026, 9:33 p.m.