Triple
T7824568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partisan Prohibitions |
E181213
|
entity |
| Predicate | typeOfVictimization |
P79212
|
FINISHED |
| Object | political persecution |
—
|
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: political persecution | Statement: [Partisan Prohibitions, typeOfVictimization, political persecution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfVictimization Context triple: [Partisan Prohibitions, typeOfVictimization, political persecution]
-
A.
typeOfAbuse
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.
portraysAsVictim
Indicates that one entity represents or depicts another entity as a victim in a given context or narrative.
-
D.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
E.
coVictim
Indicates that two or more entities are victims in the same harmful event or incident.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa0c1f5c8190b16db20daad159a1 |
completed | March 30, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:42 p.m.