Triple
T33148503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sardasht |
E848369
|
entity |
| Predicate | hasTypeOfViolenceExperienced |
P79212
|
FINISHED |
| Object | weapons of mass destruction |
—
|
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: weapons of mass destruction | Statement: [Sardasht, hasTypeOfViolenceExperienced, weapons of mass destruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfViolenceExperienced Context triple: [Sardasht, hasTypeOfViolenceExperienced, weapons of mass destruction]
-
A.
hasTypeOfViolence
Indicates that an entity involves, exhibits, or is characterized by a specific kind or category of violent behavior or action.
-
B.
usedViolenceAgainst
Indicates that one entity intentionally inflicted physical force or harm upon another entity.
-
C.
typeOfViolenceAddressed
Indicates the specific form or category of violence that is being targeted, dealt with, or addressed in a given context.
-
D.
typeOfVictimization
chosen
Indicates the specific kind or category of harmful act, abuse, or exploitation experienced by a victim.
-
E.
violationExperienced
Indicates that an entity has been subjected to or has undergone a violation, such as a breach of rights, rules, or agreed standards.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: May 1, 2026, 1:28 a.m.