Triple
T25488224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian mob |
E638770
|
entity |
| Predicate | usesViolenceFor |
P153430
|
FINISHED |
| Object | territorial control |
—
|
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: territorial control | Statement: [Russian mob, usesViolenceFor, territorial control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesViolenceFor Context triple: [Russian mob, usesViolenceFor, territorial control]
-
A.
usedViolenceFor
chosen
Indicates that an entity employed physical force or violent means in order to achieve, enable, or support a particular goal, outcome, or activity.
-
B.
containsViolence
Indicates that the subject includes, depicts, or involves acts of physical harm, aggression, or violent behavior.
-
C.
usedViolenceAgainst
Indicates that one entity intentionally inflicted physical force or harm upon another entity.
-
D.
containsGraphicViolence
Indicates that the subject includes depictions of explicit, intense, or realistic physical harm or brutality.
-
E.
justifiesViolenceThrough
Indicates that one party legitimizes or defends the use of violence by appealing to, or reasoning through, another factor, belief, or circumstance.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 2:33 p.m.