Triple
T37508645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soulrender Dormazain |
E932160
|
entity |
| Predicate | primaryVictim |
P50002
|
FINISHED |
| Object | Garrosh Hellscream |
E935491
|
NE 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: Garrosh Hellscream | Statement: [Soulrender Dormazain, primaryVictim, Garrosh Hellscream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVictim Context triple: [Soulrender Dormazain, primaryVictim, Garrosh Hellscream]
-
A.
coVictim
Indicates that two or more entities are victims in the same harmful event or incident.
-
B.
victimCategory
Indicates the classification or type of victim associated with an event, action, or harmful outcome.
-
C.
victimGroup
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
D.
isVictimOf
chosen
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
E.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
- F. None of above.
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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410404dfc48190ba23edd95e5a8b3f |
completed | June 28, 2026, 11:22 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.