Triple
T2312594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karabiner 98k |
E51991
|
entity |
| Predicate | muzzleVelocity |
P37993
|
FINISHED |
| Object | approximately 760 m/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: approximately 760 m/s | Statement: [Karabiner 98k, muzzleVelocity, approximately 760 m/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: muzzleVelocity Context triple: [Karabiner 98k, muzzleVelocity, approximately 760 m/s]
-
A.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
B.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
C.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
D.
rateOfFire
Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
-
E.
numberOfShotsFired
Indicates the total count of shots that were discharged in the described event or action.
- F. None of above. chosen
Provenance (4 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc682d094819081a96ffb77c4c42a |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:49 p.m.