Triple
T22438877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bond Arms Texas Defender |
E554699
|
entity |
| Predicate | holsterCompatibility |
P148189
|
FINISHED |
| Object | Bond Arms-specific holsters |
—
|
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: Bond Arms-specific holsters | Statement: [Bond Arms Texas Defender, holsterCompatibility, Bond Arms-specific holsters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holsterCompatibility Context triple: [Bond Arms Texas Defender, holsterCompatibility, Bond Arms-specific holsters]
-
A.
hasArrestingGear
Indicates that an entity is equipped with a system or mechanism used to rapidly decelerate and stop another entity, typically during landing or capture.
-
B.
typeOfGunMount
Indicates the specific kind or configuration of gun mounting used to support or attach a gun.
-
C.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
D.
gunType
Indicates the specific category or kind of gun associated with an entity.
-
E.
handguardFeature
Indicates that an item possesses a specific characteristic, design element, or functional attribute related to its handguard component.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae01bd08190aee5141f4c0848bc |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.