Triple
T25164702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enschede fireworks disaster |
E630139
|
entity |
| Predicate | explosionStrength |
P100776
|
FINISHED |
| Object | equivalent to 4–5 tons of TNT |
—
|
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: equivalent to 4–5 tons of TNT | Statement: [Enschede fireworks disaster, explosionStrength, equivalent to 4–5 tons of TNT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explosionStrength Context triple: [Enschede fireworks disaster, explosionStrength, equivalent to 4–5 tons of TNT]
-
A.
explosionType
Indicates the specific kind or category of explosion associated with an event or entity.
-
B.
explosivity
Indicates the degree to which something is prone to explode or cause an explosion under certain conditions.
-
C.
fireballExplosionPower
chosen
Indicates the magnitude or intensity of an explosion produced by a fireball.
-
D.
explosionDesignation
Indicates that an entity is assigned a specific designation or label associated with an explosion event or explosive classification.
-
E.
numberOfExplosions
Indicates the count of distinct explosion events associated with an entity or situation.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d412708819085a257ca1f736788 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:16 p.m.