Triple
T19349833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beretta Cx4 Storm |
E483982
|
entity |
| Predicate | recoilCharacteristic |
P128001
|
FINISHED |
| Object | low recoil |
—
|
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: low recoil | Statement: [Beretta Cx4 Storm, recoilCharacteristic, low recoil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoilCharacteristic Context triple: [Beretta Cx4 Storm, recoilCharacteristic, low recoil]
-
A.
recordCharacteristic
Indicates that an entity documents or stores a specific characteristic or attribute of another entity.
-
B.
sharedCharacteristic
Indicates that two or more entities possess the same specified attribute or quality.
-
C.
valueCharacteristic
Indicates that one entity serves as a value or specific quantitative/qualitative measure that characterizes or describes another entity.
-
D.
entityCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
E.
recordingCharacteristic
Indicates the specific qualities or attributes of how something is recorded, such as its format, medium, or technical properties.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6190381c081909c747a22422fb02c |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.