Triple
T8084279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Support Your Local Sheriff! |
E188691
|
entity |
| Predicate | violenceLevel |
P80416
|
FINISHED |
| Object | mild |
—
|
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: mild | Statement: [Support Your Local Sheriff!, violenceLevel, mild]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violenceLevel Context triple: [Support Your Local Sheriff!, violenceLevel, mild]
-
A.
hasTypeOfViolence
Indicates that an entity involves, exhibits, or is characterized by a specific kind or category of violent behavior or action.
-
B.
justifiesViolenceThrough
Indicates that one party legitimizes or defends the use of violence by appealing to, or reasoning through, another factor, belief, or circumstance.
-
C.
peakViolencePeriod
Indicates the time period during which violence reaches its highest intensity or frequency within a given context.
-
D.
usedViolenceAgainst
Indicates that one entity intentionally inflicted physical force or harm upon another entity.
-
E.
typeOfUseOfForce
Indicates the specific manner or category of force applied in an interaction or incident.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb415e61ac81909e924aea69a7ff77 |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:29 p.m.