Triple
T672759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Boston Marathon bombing |
E13008
|
entity |
| Predicate | numberOfExplosions |
P18304
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [2013 Boston Marathon bombing, numberOfExplosions, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfExplosions Context triple: [2013 Boston Marathon bombing, numberOfExplosions, 2]
-
A.
detonatedOver
Indicates that one entity caused an explosion or detonation to occur above or over another entity or location.
-
B.
explosionAltitude
Indicates the height above a reference surface at which an explosion occurs or is triggered.
-
C.
hasAltitudeOfDetonation
Indicates that an explosive event or detonation occurs at a specified altitude above a reference level (typically ground or sea level).
-
D.
numberOfInvaders
Indicates the quantity of entities classified as invaders associated with a given subject or context.
-
E.
numberLaunchedInCombat
Indicates the quantity of times an entity has been launched or deployed specifically in combat operations.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a4a1b240648190bf15415205399d97 |
completed | March 1, 2026, 8:29 p.m. |
Created at: March 1, 2026, 7:36 p.m.