Triple
T33513435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EES-VIS shared biometric matching service |
E858305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biometric matching service |
C9705
|
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: biometric matching service Context triple: [EES-VIS shared biometric matching service, instanceOf, biometric matching service]
-
A.
biometric authentication system
chosen
A biometric authentication system is a security mechanism that verifies individuals' identities by analyzing their unique biological or behavioral characteristics, such as fingerprints, facial features, or voice patterns.
-
B.
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.
-
C.
criminal history monitoring service
A criminal history monitoring service continuously tracks and updates individuals’ criminal records across relevant jurisdictions, alerting authorized parties to new charges, convictions, or changes in status.
-
D.
verification system
A verification system is a structured process or mechanism that confirms the accuracy, authenticity, or compliance of data, actions, or entities against defined criteria or standards.
-
E.
identity document technology
Identity document technology encompasses the systems, materials, and processes used to create, secure, verify, and manage official credentials that authenticate an individual’s identity.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.