Triple
T28904586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syme |
E733037
|
entity |
| Predicate | attitudeTowardViolence |
P159371
|
FINISHED |
| Object | enjoys public executions |
—
|
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: enjoys public executions | Statement: [Syme, attitudeTowardViolence, enjoys public executions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attitudeTowardViolence Context triple: [Syme, attitudeTowardViolence, enjoys public executions]
-
A.
violenceLevel
Indicates the degree or intensity of violent behavior, actions, or content present in or associated with an entity.
-
B.
attitudeTowardOthers
chosen
Indicates the nature or disposition of one entity’s feelings, judgments, or behavioral stance toward other entities.
-
C.
justifiesViolenceThrough
Indicates that one party legitimizes or defends the use of violence by appealing to, or reasoning through, another factor, belief, or circumstance.
-
D.
causeOfViolence
Indicates that one entity is the reason, trigger, or source leading to the occurrence of violence involving another entity.
-
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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 8:05 a.m.