Triple
T6467436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Valentine's Day Massacre |
E142263
|
entity |
| Predicate | resultedInDeathOf |
P51466
|
FINISHED |
| Object | members of North Side Gang |
—
|
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: members of North Side Gang | Statement: [Saint Valentine's Day Massacre, resultedInDeathOf, members of North Side Gang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultedInDeathOf Context triple: [Saint Valentine's Day Massacre, resultedInDeathOf, members of North Side Gang]
-
A.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
B.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
C.
deathOutcome
chosen
Indicates that an event, condition, or action results in the death of the affected entity.
-
D.
containsDeathOf
Indicates that the subject includes, depicts, or involves the death of the referenced entity.
-
E.
diedInCustodyOf
Indicates that an individual died while under the control, supervision, or physical custody of a specified authority or 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a12ccf481908f71f888cd744b64 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.