Triple
T36836050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturmgewehr 44 |
E910273
|
entity |
| Predicate | hasCaliberClass |
P172928
|
FINISHED |
| Object | intermediate cartridge |
—
|
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: intermediate cartridge | Statement: [Sturmgewehr 44, hasCaliberClass, intermediate cartridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaliberClass Context triple: [Sturmgewehr 44, hasCaliberClass, intermediate cartridge]
-
A.
caliberClass
chosen
Indicates a classification relationship where an entity is assigned to a specific caliber category based on its size or measurement.
-
B.
supportsCaliber
Indicates that one entity is compatible with and able to accommodate or function with a specified caliber.
-
C.
natoCaliberClass
Indicates that two ammunition types share the same standardized NATO caliber classification.
-
D.
hasArtilleryCaliber
Indicates that an artillery piece is characterized by or equipped with a specific caliber (diameter) of its gun barrel or ammunition.
-
E.
isLargerCaliberCounterpartOf
Indicates that one item is the higher-caliber version or counterpart of another, typically within the same general type or family of objects.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
Created at: May 3, 2026, 4:13 p.m.