Triple
T31071088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Restless Gun |
E791817
|
entity |
| Predicate | violencePortrayal |
P20272
|
FINISHED |
| Object | emphasis on non-lethal solutions |
—
|
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: emphasis on non-lethal solutions | Statement: [The Restless Gun, violencePortrayal, emphasis on non-lethal solutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violencePortrayal Context triple: [The Restless Gun, violencePortrayal, emphasis on non-lethal solutions]
-
A.
containsViolence
Indicates that the subject includes, depicts, or involves acts of physical harm, aggression, or violent behavior.
-
B.
containsGraphicViolence
Indicates that the subject includes depictions of explicit, intense, or realistic physical harm or brutality.
-
C.
violenceLevel
Indicates the degree or intensity of violent behavior, actions, or content present in or associated with an entity.
-
D.
viewOnViolence
chosen
Indicates an entity’s stance, opinion, or attitude toward the use of violence.
-
E.
typeOfViolenceAddressed
Indicates the specific form or category of violence that is being targeted, dealt with, or addressed in a given context.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695b566388190a0e6018bf397aa67 |
completed | May 3, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:01 p.m.