Triple
T13202969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5.56×45mm NATO |
E314285
|
entity |
| Predicate | hasTypicalMuzzleEnergy |
P107503
|
FINISHED |
| Object | ~1,700 J |
—
|
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: ~1,700 J | Statement: [5.56×45mm NATO, hasTypicalMuzzleEnergy, ~1,700 J]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalMuzzleEnergy Context triple: [5.56×45mm NATO, hasTypicalMuzzleEnergy, ~1,700 J]
-
A.
typicalMuzzleEnergy
chosen
Indicates the usual or characteristic amount of muzzle energy associated with a given weapon or ammunition type.
-
B.
muzzleVelocity
Indicates the speed at which a projectile leaves the muzzle of a firearm or similar weapon at the moment it is fired.
-
C.
hasMuzzle
Indicates that one entity possesses or is equipped with a muzzle, typically as a restraining or protective device.
-
D.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
E.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:16 p.m.