Triple
T27629765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlackBerry UEM |
E696304
|
entity |
| Predicate | securityCertification |
P63097
|
FINISHED |
| Object | FIPS 140-2 validated cryptography |
—
|
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: FIPS 140-2 validated cryptography | Statement: [BlackBerry UEM, securityCertification, FIPS 140-2 validated cryptography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityCertification Context triple: [BlackBerry UEM, securityCertification, FIPS 140-2 validated cryptography]
-
A.
typeOfCertification
Indicates the specific kind or category of certification associated with an entity.
-
B.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
C.
includesCertification
chosen
Indicates that one entity contains, lists, or encompasses a specified certification as part of its attributes or offerings.
-
D.
securityPillar
Indicates that one entity functions as a foundational security pillar or core security domain in relation to another entity.
-
E.
relatedCertification
Indicates that one certification is associated with, connected to, or relevant to another certification in some meaningful way.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 2:20 p.m.