Triple
T25922898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sirhan family |
E653218
|
entity |
| Predicate | memberInvolvedInEvent |
P130291
|
FINISHED |
| Object | Assassination of Robert F. Kennedy |
—
|
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: Assassination of Robert F. Kennedy | Statement: [Sirhan family, memberInvolvedInEvent, Assassination of Robert F. Kennedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberInvolvedInEvent Context triple: [Sirhan family, memberInvolvedInEvent, Assassination of Robert F. Kennedy]
-
A.
relativeInvolvedInEvent
chosen
Indicates that a person’s relative participates in, is affected by, or is otherwise involved in a particular event.
-
B.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
C.
participatedInEvent
Indicates that an entity took part in or was actively involved in a specific event.
-
D.
relationshipToEvent
Indicates the specific way an entity is connected or related to a particular event.
-
E.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 22, 2026, 8:35 a.m.