Triple
T38305043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hi-Point 995 carbine |
E1032321
|
entity |
| Predicate | aftermarketAccessories |
P190786
|
FINISHED |
| Object | stocks |
—
|
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: stocks | Statement: [Hi-Point 995 carbine, aftermarketAccessories, stocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aftermarketAccessories Context triple: [Hi-Point 995 carbine, aftermarketAccessories, stocks]
-
A.
aftermarketSupport
Indicates that one entity provides maintenance, service, or assistance for another entity after the initial sale or deployment.
-
B.
vehicleApplication
Indicates that an application, request, or process is specifically associated with or intended for a vehicle.
-
C.
gear
Indicates that one entity functions as a gear or toothed mechanical component that transmits motion or force to another entity.
-
D.
spares
Indicates that one entity chooses not to harm, punish, or destroy another entity when it has the power or opportunity to do so.
-
E.
performancePartsBrand
Indicates that one entity is the brand or manufacturer associated with a set of performance parts used or referenced by another entity.
- F. None of above. chosen
Provenance (4 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:30 p.m.