Triple
T18702079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine law enforcement agencies |
E457276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law enforcement agency network |
C8577
|
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 agency network Context triple: [Maine law enforcement agencies, instanceOf, law enforcement agency network]
-
A.
law enforcement agency network
chosen
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.
law enforcement agency category
A law enforcement agency category is a classification that groups agencies based on their jurisdiction, function, organizational structure, or level of authority within the legal and public safety system.
-
C.
law enforcement system
A law enforcement system is an organized framework of agencies, processes, and technologies designed to prevent, detect, investigate, and respond to violations of laws while upholding public safety and legal rights.
-
D.
law enforcement office
A law enforcement office is a physical workplace where police or other authorized agencies coordinate, manage, and support activities related to maintaining public safety and enforcing laws.
-
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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.