Triple
T5890357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Data Exchange |
E130972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law enforcement information-sharing system |
C4683
|
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: law enforcement information-sharing system Context triple: [National Data Exchange, instanceOf, law enforcement information-sharing system]
-
A.
law enforcement agency network
A law enforcement agency network is an interconnected system of local, regional, and national policing and investigative bodies that share information, resources, and coordination mechanisms to prevent, detect, and respond to crime and public safety threats.
-
B.
federal information sharing initiative
A federal information sharing initiative is a coordinated program through which federal agencies and authorized partners securely exchange data, intelligence, and best practices to improve decision-making, policy implementation, and national security.
-
C.
law enforcement tool
chosen
A law enforcement tool is any device, technology, or system used by authorities to prevent, detect, investigate, or respond to criminal activity while supporting public safety and legal compliance.
-
D.
law enforcement unit
A law enforcement unit is an organized group within a policing or security agency tasked with enforcing laws, maintaining public order, and conducting specialized operations or investigations.
-
E.
law enforcement body
A law enforcement body is an organized governmental agency responsible for maintaining public order, preventing and investigating crime, and enforcing laws within a defined jurisdiction.
- 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_69c0085628dc8190b334c1b44c067efc |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:58 p.m.