Triple
T38592459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulse Bomb |
E932484
|
entity |
| Predicate | damageApplication |
P184519
|
FINISHED |
| Object | highest damage at center of 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: highest damage at center of explosion | Statement: [Pulse Bomb, damageApplication, highest damage at center of explosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: damageApplication Context triple: [Pulse Bomb, damageApplication, highest damage at center of explosion]
-
A.
damageEffect
Indicates that one entity causes harm, reduction, or deterioration to another entity or its properties.
-
B.
damageLeadsTo
Indicates that one instance of damage causally results in or contributes to another specified outcome or condition.
-
C.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
-
D.
damageOccurred
Indicates that some form of harm, loss, or deterioration has taken place as a result of an event or action.
-
E.
damageContext
chosen
Indicates the situational or environmental circumstances under which damage occurs or is relevant in a given relationship or event.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.