Triple
T38305007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hi-Point 995 carbine |
E1032321
|
entity |
| Predicate | intendedCaliber |
P6076
|
FINISHED |
| Object | 9×19mm Parabellum |
—
|
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: 9×19mm Parabellum | Statement: [Hi-Point 995 carbine, intendedCaliber, 9×19mm Parabellum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedCaliber Context triple: [Hi-Point 995 carbine, intendedCaliber, 9×19mm Parabellum]
-
A.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
B.
isLargerCaliberCounterpartOf
Indicates that one item is the higher-caliber version or counterpart of another, typically within the same general type or family of objects.
-
C.
caliberClass
Indicates a classification relationship where an entity is assigned to a specific caliber category based on its size or measurement.
-
D.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
E.
designedForFirearm
Indicates that something is specifically created or intended to be used with a firearm.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: May 3, 2026, 4:30 p.m.