Triple
T37378589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .308 Winchester |
E928362
|
entity |
| Predicate | typicalMuzzleVelocity150gr |
P37993
|
FINISHED |
| Object | 2800 ft/s |
—
|
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: 2800 ft/s | Statement: [.308 Winchester, typicalMuzzleVelocity150gr, 2800 ft/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMuzzleVelocity150gr Context triple: [.308 Winchester, typicalMuzzleVelocity150gr, 2800 ft/s]
-
A.
muzzleVelocity
chosen
Indicates the speed at which a projectile leaves the muzzle of a firearm or similar weapon at the moment it is fired.
-
B.
typicalMuzzleEnergy
Indicates the usual or characteristic amount of muzzle energy associated with a given weapon or ammunition type.
-
C.
standardBulletWeight
Indicates the typical or commonly accepted mass of a given type of bullet under standard specifications.
-
D.
muzzleType
Indicates the specific style or configuration of a muzzle associated with an entity, such as a weapon or animal.
-
E.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.