Triple
T28309227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .300 AAC Blackout |
E713950
|
entity |
| Predicate | typicalSubsonicBulletWeight |
P107501
|
FINISHED |
| Object | 190–220 grains |
—
|
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: 190–220 grains | Statement: [.300 AAC Blackout, typicalSubsonicBulletWeight, 190–220 grains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSubsonicBulletWeight Context triple: [.300 AAC Blackout, typicalSubsonicBulletWeight, 190–220 grains]
-
A.
standardBulletWeight
chosen
Indicates the typical or commonly accepted mass of a given type of bullet under standard specifications.
-
B.
munitionWeightCategory
Indicates the classification of a munition based on its weight range or weight-related category.
-
C.
typicalRifleWeightLimit
Indicates the maximum weight that is generally considered standard or acceptable for a typical rifle.
-
D.
typicalMuzzleEnergy
Indicates the usual or characteristic amount of muzzle energy associated with a given weapon or ammunition type.
-
E.
missileWeight
Indicates the weight or mass associated with a missile in the relationship.
- 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_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: April 27, 2026, 11:39 p.m.