Triple
T28309183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .223 Remington |
E713949
|
entity |
| Predicate | typicalMuzzleEnergyRange |
P107503
|
FINISHED |
| Object | 1100–1300 ft⋅lbf |
—
|
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: 1100–1300 ft⋅lbf | Statement: [.223 Remington, typicalMuzzleEnergyRange, 1100–1300 ft⋅lbf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMuzzleEnergyRange Context triple: [.223 Remington, typicalMuzzleEnergyRange, 1100–1300 ft⋅lbf]
-
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.
muzzleType
Indicates the specific style or configuration of a muzzle associated with an entity, such as a weapon or animal.
-
D.
typicalShootingDistances
Indicates the usual or standard distances at which shooting (e.g., with a weapon or camera) typically occurs in a given context.
-
E.
hasFiringRange
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
- 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_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
Created at: April 27, 2026, 11:39 p.m.