Triple
T743143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gadget |
E15286
|
entity |
| Predicate | usedExplosives |
P820
|
FINISHED |
| Object | conventional high explosives for implosion |
—
|
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: conventional high explosives for implosion | Statement: [The Gadget, usedExplosives, conventional high explosives for implosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedExplosives Context triple: [The Gadget, usedExplosives, conventional high explosives for implosion]
-
A.
numberOfExplosions
Indicates the count of distinct explosion events associated with an entity or situation.
-
B.
weaponsUsed
chosen
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
C.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
D.
detonatedOver
Indicates that one entity caused an explosion or detonation to occur above or over another entity or location.
-
E.
bombLoad
Indicates the amount or configuration of bombs carried by an entity, typically an aircraft, for a mission or operation.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a60f92d08190a4f44c5b4d068ab5 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fdaaf48190985f62acfc069508 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.