Triple
T28309182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .223 Remington |
E713949
|
entity |
| Predicate | typicalMuzzleVelocityRange |
P37993
|
FINISHED |
| Object | 2700–3300 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: 2700–3300 ft/s | Statement: [.223 Remington, typicalMuzzleVelocityRange, 2700–3300 ft/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMuzzleVelocityRange Context triple: [.223 Remington, typicalMuzzleVelocityRange, 2700–3300 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.
muzzleType
Indicates the specific style or configuration of a muzzle associated with an entity, such as a weapon or animal.
-
D.
rangeStandardAmmunition
Indicates that the relationship specifies the standard type of ammunition used for a given range or weapon system.
-
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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
Created at: April 27, 2026, 11:39 p.m.