Triple
T672762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Boston Marathon bombing |
E13008
|
entity |
| Predicate | injured |
P3816
|
FINISHED |
| Object | hundreds |
—
|
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: hundreds | Statement: [2013 Boston Marathon bombing, injured, hundreds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: injured Context triple: [2013 Boston Marathon bombing, injured, hundreds]
-
A.
causeOfInjury
Indicates that one entity is the source or reason that another entity sustained an injury.
-
B.
hasInjuries
chosen
Indicates that an entity has sustained one or more physical or bodily injuries.
-
C.
damagedIn
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
-
D.
injuryInvolvedPlayer
Indicates that a specific player is involved in, affected by, or associated with a particular injury event.
-
E.
fatalInjury
Indicates that an entity causes or sustains an injury that directly results in death.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a1b3682c8190a9b9a454480c3446 |
completed | March 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69a49d1a16c48190af89e3b078a4957e |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.