Triple
T38526813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATF firearms tracing databases |
E923249
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | firearms tracing database system |
C29967
|
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: firearms tracing database system Context triple: [ATF firearms tracing databases, instanceOf, firearms tracing database system]
-
A.
online firearms tracing system
chosen
An online firearms tracing system is a digital platform that enables authorized agencies to track and analyze the history, ownership, and movement of firearms from manufacture to recovery in support of law enforcement investigations.
-
B.
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.
-
C.
firearm background check system
A firearm background check system is a software and procedural framework that verifies an individual's legal eligibility to purchase or possess a firearm by querying criminal, mental health, and other relevant records before approving or denying the transaction.
-
D.
firearm
A firearm is a portable weapon that uses confined explosive force to propel a projectile through a barrel toward a target.
-
E.
criminal justice information system
A criminal justice information system is an integrated platform that collects, manages, and shares data related to crimes, offenders, victims, and justice processes among law enforcement, courts, and correctional agencies.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.