Triple

T22475709
Position Surface form Disambiguated ID Type / Status
Subject United Nations Security Council Resolution 1960 E555623 entity
Predicate typeOfViolenceAddressed P148347 FINISHED
Object rape in armed conflict 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: rape in armed conflict | Statement: [United Nations Security Council Resolution 1960, typeOfViolenceAddressed, rape in armed conflict]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfViolenceAddressed
Context triple: [United Nations Security Council Resolution 1960, typeOfViolenceAddressed, rape in armed conflict]
  • A. hasTypeOfViolence
    Indicates that an entity involves, exhibits, or is characterized by a specific kind or category of violent behavior or action.
  • B. typeOfVictimization
    Indicates the specific kind or category of harmful act, abuse, or exploitation experienced by a victim.
  • C. usedViolenceAgainst
    Indicates that one entity intentionally inflicted physical force or harm upon another entity.
  • D. positionOnViolence
    Indicates a stance, attitude, or policy that an entity holds regarding the use, justification, or acceptability of violence.
  • E. typeOfAbuse
    Indicates the specific kind or category of abusive behavior that one entity inflicts on another.
  • 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_69e11e52c2048190952dc5df209b9bed completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15be3930c8190ba967196df7e083f completed April 29, 2026, 1:16 a.m.
PD Predicate disambiguation batch_69e898b6eee08190ba673a0ee329e671 completed April 22, 2026, 9:45 a.m.
PDg Predicate description generation batch_69e8aa39e3388190b659d59948ebf3e6 completed April 22, 2026, 11 a.m.
Created at: April 16, 2026, 8:49 p.m.