Triple
T26688879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branch 227 (Damascus region branch) |
E672820
|
entity |
| Predicate | typeOfAbuseDocumented |
P36524
|
FINISHED |
| Object | beatings |
—
|
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: beatings | Statement: [Branch 227 (Damascus region branch), typeOfAbuseDocumented, beatings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAbuseDocumented Context triple: [Branch 227 (Damascus region branch), typeOfAbuseDocumented, beatings]
-
A.
typeOfAbuse
chosen
Indicates the specific kind or category of abusive behavior that one entity inflicts on another.
-
B.
hasTypeOfViolence
Indicates that an entity involves, exhibits, or is characterized by a specific kind or category of violent behavior or action.
-
C.
typeOfViolenceAddressed
Indicates the specific form or category of violence that is being targeted, dealt with, or addressed in a given context.
-
D.
periodOfAbuse
Indicates the time span during which abusive behavior occurred or was experienced.
-
E.
typeOfVictimization
Indicates the specific kind or category of harmful act, abuse, or exploitation experienced by a victim.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 27, 2026, 3:24 a.m.