NEXYTE Product Description Page 12 preparatory steps for analysis, automatic entity extraction, enrichment, and translation. − Media modeling. NEXYTE applies specialized handling of multimedia files such as videos, images, audio files, etc. NEXYTE extracts and registers all metadata from these files and applies image or video analytics. Media files that are extracted from the collected data are linked to the related person entity or investigation based on identification details. If no details are available, or no relevant person/investigation is found, the media file is stored as an independent entity within the system. + Security-based considerations. When adding data sources to the system, the modeling and retention steps take into consideration future access and permission needs. By marking the source of each data component, the system secures future permission-based access to case- or source-specific information. 3.2 Entity Resolution An entity includes a set of aggregative views that create a complete picture of an investigated interest, such as a person, organization, phone device, etc. Entity resolution applies to the matching and fusion of contents belonging to the same entity. This is an essential step in the creation of logical entities, so that all information about a specific person, organization or event is concentrated in a unified entity view to the user. For structured content, identifiers from different sources are automatically matched to correlate dispersed sources into a single entity and provide a unified entity view for the user. Unstructured content is processed at access and ingestion, automatically identifying entities in the sources (e.g., names, car’s license plate) and surfacing suggested correlations to entities in the system. Outcomes Safeguards An entity may have several types of identifiers, some of which may even have multiple values. For example, a person can have one Social Security Number (SSN), several Passport numbers, and one Taxpayer number. When dealing with multiple types and values of identifiers in a world where identities are sometimes stolen and data is sometimes partial - NEXYTE balances between the need to fuse identifiers into a single entity, and avoiding data loss when conflicts in data occur. For that purpose, each entity type should have a single identifier which represents its core being (a "unique" identifier) - this will be the identifier which determines if entities should be merged or not. The other identifiers will be considered "strong" or "weak" but even though they are not unique, these identifiers can contribute to the resolution of an entity by adding and scoring them. A permitted user also has the ability to manually edit certain properties and relations, or to add an insight to highlight concerns if they believe there are data inconsistencies or faulty data attributed to an entity.