Triple
T13834146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandy Hook Elementary School |
E332479
|
entity |
| Predicate | typeOfAttackIn2012Shooting |
P4333
|
FINISHED |
| Object | school shooting |
—
|
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: school shooting | Statement: [Sandy Hook Elementary School, typeOfAttackIn2012Shooting, school shooting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAttackIn2012Shooting Context triple: [Sandy Hook Elementary School, typeOfAttackIn2012Shooting, school shooting]
-
A.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
numberOfPeopleShot
Indicates the count of individuals who were shot in a particular event or context.
-
C.
allegedShooterLocation
Indicates the place where a person is claimed or reported to have carried out a shooting.
-
D.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
E.
typeOfKilling
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de029a34bc8190ae892ef7b09fc9e9 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.