Triple
T25164708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enschede fireworks disaster |
E630139
|
entity |
| Predicate | typeOfMaterialInvolved |
P25885
|
FINISHED |
| Object | consumer fireworks |
—
|
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: consumer fireworks | Statement: [Enschede fireworks disaster, typeOfMaterialInvolved, consumer fireworks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMaterialInvolved Context triple: [Enschede fireworks disaster, typeOfMaterialInvolved, consumer fireworks]
-
A.
materialInvolved
chosen
Indicates that a particular material participates in, is used by, or is otherwise involved in the referenced process, event, or relationship.
-
B.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
testedMaterial
Indicates that an entity has been used as the material or substance on which a test or experiment was performed.
-
D.
materialFormedIn
Indicates that a material is created, produced, or formed within a specified process, environment, or context.
-
E.
suppliedMaterialType
Indicates the type or category of material that is provided or supplied in a given context.
- 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_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 21, 2026, 12:16 p.m.