Triple

T28757079
Position Surface form Disambiguated ID Type / Status
Subject Chrysippus E731699 entity
Predicate curseConnection P7531 FINISHED
Object his death is linked to 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: his death is linked to the curse on the House of Atreus | Statement: [Chrysippus, curseConnection, his death is linked to the curse on the House of Atreus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: curseConnection
Context triple: [Chrysippus, curseConnection, his death is linked to the curse on the House of Atreus]
  • A. curseTrigger
    Indicates that one entity causes, activates, or is responsible for initiating a curse that affects another entity.
  • B. curseCondition
    Indicates a condition or state in which an entity is affected by a curse or cursed effect.
  • C. curseSymbol
    Indicates that one entity serves as a symbol, sign, or representation of a curse associated with another entity.
  • D. associatedCurse chosen
    Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
  • E. attemptedCurseReversal
    Indicates an action where one entity tried, but did not necessarily succeed, to reverse or undo a curse affecting another 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_69f043ed68a881909e858a06bab7a247 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f658ee40088190b71e1219407690d0 completed May 2, 2026, 8:05 p.m.
PD Predicate disambiguation batch_69f65760fd3081908ffe014a5e2bf069 completed May 2, 2026, 7:58 p.m.
Created at: April 28, 2026, 6:10 a.m.