Triple
T11247219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die by the Sword |
E266236
|
entity |
| Predicate | hasViolence |
P81921
|
FINISHED |
| Object | graphic dismemberment |
—
|
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: graphic dismemberment | Statement: [Die by the Sword, hasViolence, graphic dismemberment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViolence Context triple: [Die by the Sword, hasViolence, graphic dismemberment]
-
A.
containsGraphicViolence
chosen
Indicates that the subject includes depictions of explicit, intense, or realistic physical harm or brutality.
-
B.
violenceLevel
Indicates the degree or intensity of violent behavior, actions, or content present in or associated with an entity.
-
C.
hasTypeOfViolence
Indicates that an entity involves, exhibits, or is characterized by a specific kind or category of violent behavior or action.
-
D.
justifiesViolenceThrough
Indicates that one party legitimizes or defends the use of violence by appealing to, or reasoning through, another factor, belief, or circumstance.
-
E.
peakViolencePeriod
Indicates the time period during which violence reaches its highest intensity or frequency within 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e91d1484819098ee6b2efb5316a5 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.