Triple
T11404613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serena |
E270203
|
entity |
| Predicate | reactsToEvent |
P17506
|
FINISHED |
| Object | Robbins’s killing at the craps game |
—
|
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: Robbins’s killing at the craps game | Statement: [Serena, reactsToEvent, Robbins’s killing at the craps game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactsToEvent Context triple: [Serena, reactsToEvent, Robbins’s killing at the craps game]
-
A.
dealtWithEvent
chosen
Indicates that an entity has handled, responded to, or otherwise taken action to address a particular event.
-
B.
interpretsEvent
Indicates that an entity analyzes and assigns meaning or significance to an event.
-
C.
exposesEvent
Indicates that one entity makes an event available or visible for use, handling, or observation by another entity or system.
-
D.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
-
E.
eventTarget
Indicates that an event is directed toward, affects, or is intended for a particular target entity.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014ab46881909fa1d425926c617b |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.