Triple

T36739799
Position Surface form Disambiguated ID Type / Status
Subject M&P series firearms E907577 entity
Predicate productLineIncludes P11218 FINISHED
Object M&P Bodyguard 380
The M&P Bodyguard 380 is a compact, polymer-framed .380 ACP semi-automatic pistol from Smith & Wesson designed primarily for concealed carry and personal defense.
E2206695 NE 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: M&P Bodyguard 380 | Statement: [M&P series firearms, productLineIncludes, M&P Bodyguard 380]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: M&P Bodyguard 380
Triple: [M&P series firearms, productLineIncludes, M&P Bodyguard 380]
Generated description
The M&P Bodyguard 380 is a compact, polymer-framed .380 ACP semi-automatic pistol from Smith & Wesson designed primarily for concealed carry and personal defense.

Provenance (5 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_69f76e75aa6881909b844d00a3888ee5 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c8fe417881908a7d3c47c6965e4b completed May 3, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3e2c1c34fc8190a6756dc0baa1cdc0 completed June 26, 2026, 7:37 a.m.
NEDg Description generation batch_6a3e3003356881909ebce7b7e2c31d8d completed June 26, 2026, 7:53 a.m.
NED2 Entity disambiguation (via description) batch_6a3e44bdce608190a508f2da4f9710e9 completed June 26, 2026, 9:22 a.m.
Created at: May 3, 2026, 4:12 p.m.