Triple

T14536858
Position Surface form Disambiguated ID Type / Status
Subject Fiona E341065 entity
Predicate curseBrokenBy P7531 FINISHED
Object true love's kiss with Shrek 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: true love's kiss with Shrek | Statement: [Fiona, curseBrokenBy, true love's kiss with Shrek]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: curseBrokenBy
Context triple: [Fiona, curseBrokenBy, true love's kiss with Shrek]
  • A. curseCondition
    Indicates a condition or state in which an entity is affected by a curse or cursed effect.
  • B. attemptedCurseReversal
    Indicates an action where one entity tried, but did not necessarily succeed, to reverse or undo a curse affecting another entity.
  • C. spontaneouslyBrokenBy
    Indicates that a symmetry or property is not explicitly violated by the underlying laws but is instead broken by the system’s ground state or configuration due to spontaneous symmetry breaking caused by the specified entity or mechanism.
  • D. associatedCurse chosen
    Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
  • E. isBrokenBy
    Indicates that one entity causes another entity to become damaged, nonfunctional, or destroyed.
  • 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_69d822dac79c8190a84a073f3cbaced5 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb1bb90008190947ac0961393446d completed April 14, 2026, 9:29 p.m.
PD Predicate disambiguation batch_69de5c546c7081909e27d504ec360c5c completed April 14, 2026, 3:25 p.m.
Created at: April 10, 2026, 1:22 a.m.