Triple

T33735025
Position Surface form Disambiguated ID Type / Status
Subject Sammy Younge Jr. E864389 entity
Predicate killedFor P134344 FINISHED
Object attempting to desegregate a whites-only restroom 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: attempting to desegregate a whites-only restroom | Statement: [Sammy Younge Jr., killedFor, attempting to desegregate a whites-only restroom]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: killedFor
Context triple: [Sammy Younge Jr., killedFor, attempting to desegregate a whites-only restroom]
  • A. killedBecauseOf chosen
    Indicates that one entity killed another specifically due to a particular reason, motive, or triggering factor associated with that other entity or a related circumstance.
  • B. killedBy
    Indicates that one entity caused the death of another entity.
  • C. killedDuring
    Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
  • D. killedOnBehalfOf
    Indicates that one entity carried out a killing as a representative of, or in service to, another entity.
  • E. killedAlongWith
    Indicates that one entity was killed at the same time and in the same event or circumstance as 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_69f3498a64cc8190b4b414c67b280d93 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fb25570481908be273a261c1933e completed May 3, 2026, 7:37 a.m.
PD Predicate disambiguation batch_69f6f96dd4c8819093d6a7bd046a9ad5 completed May 3, 2026, 7:29 a.m.
Created at: May 1, 2026, 1:44 a.m.