Triple
T37421794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MK19 grenade launcher |
E929874
|
entity |
| Predicate | standardUSDesignation |
P97629
|
FINISHED |
| Object | MK19 Mod 3 |
—
|
NE NERFINISHED |
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: MK19 Mod 3 | Statement: [MK19 grenade launcher, standardUSDesignation, MK19 Mod 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardUSDesignation Context triple: [MK19 grenade launcher, standardUSDesignation, MK19 Mod 3]
-
A.
americanDesignation
chosen
Indicates that one entity is the official American name, title, or designation for another entity.
-
B.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
C.
standardUSNATOCaliber
Indicates that an item’s caliber conforms to the standard ammunition dimensions used by U.S. and NATO military forces.
-
D.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
E.
standardUse
Indicates that something is used in a typical, expected, or officially accepted manner for its intended purpose.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 3, 2026, 4:16 p.m.