Triple
T32517606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LifeLock |
E831100
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | identity theft protection company |
C27279
|
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: identity theft protection company Context triple: [LifeLock, instanceOf, identity theft protection company]
-
A.
security technology company
chosen
A security technology company develops and provides advanced tools, systems, and services to protect people, data, and assets from physical and digital threats.
-
B.
cybersecurity identifier
A cybersecurity identifier is a unique label or token used to recognize, track, or reference specific digital entities, events, vulnerabilities, or threats within security systems and processes.
-
C.
identity verification platform
An identity verification platform is a system that securely validates and authenticates individuals’ identities using documents, biometrics, and data checks to prevent fraud and ensure trust in digital interactions.
-
D.
brand protection company
A brand protection company monitors, detects, and enforces against unauthorized or infringing use of a brand’s intellectual property across physical and digital channels to safeguard reputation and revenue.
-
E.
privacy protection software
Privacy protection software is a class of applications designed to safeguard users' personal data and online activities by controlling access, encrypting information, and preventing unauthorized tracking or disclosure.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.