Triple
T35996441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy War (Święta Wojna) Kraków derby |
E1040999
|
entity |
| Predicate | hasViolenceRisk |
P80416
|
FINISHED |
| Object | elevated |
—
|
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: elevated | Statement: [Holy War (Święta Wojna) Kraków derby, hasViolenceRisk, elevated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViolenceRisk Context triple: [Holy War (Święta Wojna) Kraków derby, hasViolenceRisk, elevated]
-
A.
hasTypeOfViolence
Indicates that an entity involves, exhibits, or is characterized by a specific kind or category of violent behavior or action.
-
B.
containsViolence
Indicates that the subject includes, depicts, or involves acts of physical harm, aggression, or violent behavior.
-
C.
violenceLevel
chosen
Indicates the degree or intensity of violent behavior, actions, or content present in or associated with an entity.
-
D.
usedViolenceFor
Indicates that an entity employed physical force or violent means in order to achieve, enable, or support a particular goal, outcome, or activity.
-
E.
causeOfViolence
Indicates that one entity is the reason, trigger, or source leading to the occurrence of violence involving another entity.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:07 p.m.