Triple

T29432042
Position Surface form Disambiguated ID Type / Status
Subject Sarah E746456 entity
Predicate originOfTrauma P168492 FINISHED
Object pre-film personal tragedy (implied in narrative) 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: pre-film personal tragedy (implied in narrative) | Statement: [Sarah, originOfTrauma, pre-film personal tragedy (implied in narrative)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originOfTrauma
Context triple: [Sarah, originOfTrauma, pre-film personal tragedy (implied in narrative)]
  • A. traumaSource chosen
    Indicates that one entity is the origin or cause of another entity’s trauma.
  • B. trauma
    Indicates that an entity has experienced a deeply distressing or harmful event or series of events that cause lasting psychological or emotional impact.
  • C. causeOfInjury
    Indicates that one entity is the source or reason that another entity sustained an injury.
  • D. traumaLevel
    Indicates the degree or severity of trauma experienced or present in relation to an entity or event.
  • E. traumaTheme
    Indicates that the relationship or context involves themes of trauma, such as psychological injury, distressing experiences, or their emotional and narrative impact.
  • 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_69f0a7a06e0081908add494075912eb4 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69ff9bed58dc8190a204816d4ed6c32c completed May 9, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69ff9b69653c81908ab0d88055a66a88 completed May 9, 2026, 8:39 p.m.
Created at: April 28, 2026, 3:14 p.m.