Triple
T35581215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-64 pistol |
E1028226
|
entity |
| Predicate | holsterType |
P183422
|
FINISHED |
| Object | military flap holster |
—
|
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: military flap holster | Statement: [P-64 pistol, holsterType, military flap holster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holsterType Context triple: [P-64 pistol, holsterType, military flap holster]
-
A.
holsterCompatibility
Indicates that one item can be securely carried or stored in a particular holster designed to fit it.
-
B.
typeOfGunMount
Indicates the specific kind or configuration of gun mounting used to support or attach a gun.
-
C.
cartridgeCaseType
Indicates the specific type or classification of a cartridge case associated with an item or entity.
-
D.
handguardFeature
Indicates that an item possesses a specific characteristic, design element, or functional attribute related to its handguard component.
-
E.
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.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.