Triple
T21476120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VPRS |
E529864
|
entity |
| Predicate | typeOfVictimCovered |
P142550
|
FINISHED |
| Object | individual victims |
—
|
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: individual victims | Statement: [VPRS, typeOfVictimCovered, individual victims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfVictimCovered Context triple: [VPRS, typeOfVictimCovered, individual victims]
-
A.
hasTypeOfVictims
chosen
Indicates that an entity is associated with victims of a specified type or category.
-
B.
coVictim
Indicates that two or more entities are victims in the same harmful event or incident.
-
C.
proportionOfVictims
Indicates the quantitative share or fraction that victims represent within a larger referenced group or total.
-
D.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
E.
hasTypicalVictimRole
Indicates that an entity typically occupies the role of a victim in the context of a particular action, event, or relationship.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1737f881908ef7889e9568a4d3 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:20 p.m.