Triple
T16702585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firefox Monitor |
E405888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data breach notification service |
C25443
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: data breach notification service Context triple: [Firefox Monitor, instanceOf, data breach notification service]
-
A.
risk and compliance data service
A risk and compliance data service aggregates, analyzes, and delivers regulatory, risk, and compliance-related information to help organizations identify exposures, meet legal obligations, and support informed governance decisions.
-
B.
credential harvesting tool
A credential harvesting tool is a malicious software or system designed to illicitly collect and store users’ authentication data, such as usernames, passwords, and tokens, often through phishing, keylogging, or exploiting insecure interfaces.
-
C.
cybersecurity incident
A cybersecurity incident is any event that compromises or attempts to compromise the confidentiality, integrity, or availability of information systems, networks, or data through unauthorized access, misuse, disruption, or destruction.
-
D.
data protection solution
A data protection solution is a system or set of tools and practices designed to safeguard data from loss, corruption, unauthorized access, and misuse throughout its lifecycle.
-
E.
notification management feature
chosen
A notification management feature allows users to configure, prioritize, and control how, when, and which alerts or messages they receive across an application.
- F. None of above.
Provenance (1 batch)
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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.