Triple
T15858127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C96 pistol |
E384512
|
entity |
| Predicate | originalCaliber |
P6076
|
FINISHED |
| Object | 7.63×25mm Mauser |
—
|
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: 7.63×25mm Mauser | Statement: [C96 pistol, originalCaliber, 7.63×25mm Mauser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCaliber Context triple: [C96 pistol, originalCaliber, 7.63×25mm Mauser]
-
A.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
B.
successorCaliber
Indicates that one entity serves as the successor or follow-up version in terms of quality, standard, or specification relative to another.
-
C.
barrelLengthInCalibers
Indicates the length of a barrel expressed as a multiple of its bore diameter (in calibers), describing how many times the bore diameter fits into the barrel length.
-
D.
natoCaliberClass
Indicates that two ammunition types share the same standardized NATO caliber classification.
-
E.
originalSide
Indicates that an entity remains on or is associated with its initial or starting side in a given context or 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_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.