Triple

T2514442
Position Surface form Disambiguated ID Type / Status
Subject Myrtilus E52778 entity
Predicate mythicFunction P9987 FINISHED
Object originator of the curse on the House of Atreus LITERAL 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: originator of the curse on the House of Atreus | Statement: [Myrtilus, mythicFunction, originator of the curse on the House of Atreus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mythicFunction
Context triple: [Myrtilus, mythicFunction, originator of the curse on the House of Atreus]
  • A. mythicReputation
    Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
  • B. mythologicalGeneration
    Indicates a generational relationship in mythology, where one mythological being or group descends from or follows another in a lineage or succession.
  • C. mythologicalEvent
    Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
  • D. mythologicalRole chosen
    Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
  • E. hasMythicMotif
    Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
  • F. None of above.

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_69ab4958e76481908a235377dd921c9e completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd5a33234819082ad49fa6594b6be completed March 7, 2026, 7:37 a.m.
PD Predicate disambiguation batch_69abd0bf37c0819088d28b5081ba7556 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:46 p.m.