Triple
T34810967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | assassination of Robert F. Kennedy |
E1003495
|
entity |
| Predicate | otherVictim |
P31963
|
FINISHED |
| Object | Paul Schrade |
—
|
NE NERFINISHED |
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: Paul Schrade | Statement: [assassination of Robert F. Kennedy, otherVictim, Paul Schrade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherVictim Context triple: [assassination of Robert F. Kennedy, otherVictim, Paul Schrade]
-
A.
coVictim
chosen
Indicates that two or more entities are victims in the same harmful event or incident.
-
B.
victimWas
Indicates that one entity was the victim of an action, event, or harmful behavior carried out by another entity.
-
C.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
D.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
-
E.
allegedVictimOf
Indicates that one entity is claimed or reported to have been harmed, wronged, or victimized by another entity, without asserting that the claim is proven.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 3:59 p.m.