Triple
T29422794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BONUS artillery round |
E746198
|
entity |
| Predicate | submunitionEffect |
P46849
|
FINISHED |
| Object | explosively formed penetrator |
—
|
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: explosively formed penetrator | Statement: [BONUS artillery round, submunitionEffect, explosively formed penetrator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submunitionEffect Context triple: [BONUS artillery round, submunitionEffect, explosively formed penetrator]
-
A.
warheadEffect
chosen
Indicates the type or nature of impact, damage, or outcome produced when a warhead is used or detonated.
-
B.
submunitionGuidanceSensors
Indicates that the submunition is equipped with sensors used to guide or adjust its trajectory toward a target.
-
C.
explosionDesignation
Indicates that an entity is assigned a specific designation or label associated with an explosion event or explosive classification.
-
D.
explosionMechanism
Indicates the specific process or mechanism by which an explosion is initiated or occurs.
-
E.
bombDamage
Indicates that one entity has caused damage to another entity through the use or effects of a bomb.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a6aa3d08190887bfa4eed48faeb |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:07 p.m.