Triple

T28929989
Position Surface form Disambiguated ID Type / Status
Subject SD Snatcher E733753 entity
Predicate violenceLevelComparedToOriginal P166030 FINISHED
Object less graphic than Snatcher 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: less graphic than Snatcher | Statement: [SD Snatcher, violenceLevelComparedToOriginal, less graphic than Snatcher]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: violenceLevelComparedToOriginal
Context triple: [SD Snatcher, violenceLevelComparedToOriginal, less graphic than Snatcher]
  • A. violenceLevel
    Indicates the degree or intensity of violent behavior, actions, or content present in or associated with an entity.
  • B. containsViolence
    Indicates that the subject includes, depicts, or involves acts of physical harm, aggression, or violent behavior.
  • C. containsGraphicViolence
    Indicates that the subject includes depictions of explicit, intense, or realistic physical harm or brutality.
  • D. violenceLedTo
    Indicates that an act or state of violence caused or directly resulted in a subsequent event, condition, or outcome.
  • E. usedViolenceFor
    Indicates that an entity employed physical force or violent means in order to achieve, enable, or support a particular goal, outcome, or activity.
  • F. None of above. chosen

Provenance (4 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_69f05b0b49b08190b8994b339c7980f6 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f65bb75cd08190bbdb63c093ad6210 completed May 2, 2026, 8:16 p.m.
PD Predicate disambiguation batch_69f659d02f1c8190831758ac52bb54e4 completed May 2, 2026, 8:08 p.m.
PDg Predicate description generation batch_69f65b136b30819090cf59fb772f35f1 completed May 2, 2026, 8:14 p.m.
Created at: April 28, 2026, 8:27 a.m.