Triple
T33513099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Dactyloscopy system |
E858298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fingerprint database |
C8594
|
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: fingerprint database Context triple: [European Dactyloscopy system, instanceOf, fingerprint database]
-
A.
biometric authentication system
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.
FBI file
An FBI file is an official collection of records, reports, and investigative materials compiled and maintained by the Federal Bureau of Investigation about a person, organization, event, or case.
-
C.
federal government database
chosen
A federal government database is a centralized, secure digital repository used by national government agencies to store, manage, and retrieve official records, data, and information for administrative, regulatory, and public service purposes.
-
D.
federal government database
A federal government database is a centralized, electronically managed collection of structured data maintained by national government agencies to store, process, and retrieve information for administrative, regulatory, and public service purposes.
-
E.
firearms licensing database
A firearms licensing database is a centralized system that securely stores, manages, and tracks information about firearm licenses, applicants, approvals, renewals, and related regulatory compliance records.
- 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.