Triple
T36961694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beheaded Kamikaze |
E914322
|
entity |
| Predicate | hasExplosiveType |
P100269
|
FINISHED |
| Object | area-of-effect explosion |
—
|
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: area-of-effect explosion | Statement: [Beheaded Kamikaze, hasExplosiveType, area-of-effect explosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExplosiveType Context triple: [Beheaded Kamikaze, hasExplosiveType, area-of-effect explosion]
-
A.
explosionType
chosen
Indicates the specific kind or category of explosion associated with an event or entity.
-
B.
explosiveClass
Indicates the classification or category assigned to an explosive based on its type, properties, or regulatory class.
-
C.
explosiveLensType
Indicates the specific design or configuration of the explosive lens used to shape and direct the detonation wave.
-
D.
hasFrequentExplosions
Indicates that the subject regularly experiences or produces explosions occurring at short or recurring intervals.
-
E.
hasHeatOfExplosion
Indicates that an entity possesses a specified amount or measure of energy released as heat during an explosive reaction.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:14 p.m.