Triple
T8131349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HK69 grenade launcher |
E189858
|
entity |
| Predicate | intendedMunitionType |
P6074
|
FINISHED |
| Object | explosive grenades |
—
|
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: explosive grenades | Statement: [HK69 grenade launcher, intendedMunitionType, explosive grenades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedMunitionType Context triple: [HK69 grenade launcher, intendedMunitionType, explosive grenades]
-
A.
ammunitionType
chosen
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
B.
missileTypeCarried
Indicates the specific type or category of missile that is carried by a given platform, launcher, or delivery system.
-
C.
weaponTypeDelivered
Indicates that a specific type of weapon has been delivered from one entity to another.
-
D.
weaponTypeTested
Indicates that a specific type of weapon has been subjected to a test or evaluation in the described context.
-
E.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
- 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_69ca82bcb4848190a9a9d036ad768642 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:34 p.m.