Triple
T36835971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturmgewehr family of rifles |
E910271
|
entity |
| Predicate | keyDesignFeature |
P7153
|
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 family of rifles, keyDesignFeature, intermediate cartridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyDesignFeature Context triple: [Sturmgewehr family of rifles, keyDesignFeature, intermediate cartridge]
-
A.
keyFeature
chosen
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
B.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
C.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
-
D.
keyDesigner
Indicates that an entity serves as the primary or lead designer responsible for creating or shaping another entity.
-
E.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
- 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_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.