Triple
T15858152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C96 pistol |
E384512
|
entity |
| Predicate | Red 9 C96Chambering |
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: [C96 pistol, Red 9 C96Chambering, 9×19mm Parabellum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Red 9 C96Chambering Context triple: [C96 pistol, Red 9 C96Chambering, 9×19mm Parabellum]
-
A.
isServiceRifleOf
Indicates that one entity is the designated service rifle used by another entity, typically a military or armed force.
-
B.
Berdan No.1 rifle
Indicates that an entity is a Berdan No.1 rifle, i.e., it has the identity or classification of that specific rifle model.
-
C.
isGasOperated
Indicates that an entity functions or operates using gas as its primary power or energy source.
-
D.
hasChamber
Indicates that one entity possesses, contains, or is associated with a distinct enclosed space or compartment (a chamber).
-
E.
gunCalibre
chosen
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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:50 a.m.