Triple
T29199954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G3A3 |
E740239
|
entity |
| Predicate | buttstockFeatures |
P164135
|
FINISHED |
| Object | rubber buttpad |
—
|
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: rubber buttpad | Statement: [G3A3, buttstockFeatures, rubber buttpad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buttstockFeatures Context triple: [G3A3, buttstockFeatures, rubber buttpad]
-
A.
buttstockFeature
chosen
Indicates that one entity has a specific characteristic, design element, or functional attribute related to a buttstock.
-
B.
buttstockMaterial
Indicates the material from which the buttstock of an object (typically a firearm) is made.
-
C.
buttstockAdjustability
Indicates whether and how the buttstock of a firearm can be adjusted (e.g., for length, height, or angle) relative to the rest of the weapon.
-
D.
spanCharacteristic
Indicates that one entity has a particular measurable or descriptive property that characterizes the extent, duration, or range of another entity or phenomenon.
-
E.
beltFeature
Indicates that an entity possesses or is characterized by a specific belt-related attribute or component.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c4c37481908462be4bbede5a2b |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:06 p.m.