Triple
T30962391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codes of Practice for Police Officers in England and Wales |
E788864
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | policing code of practice |
C59799
|
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: policing code of practice Context triple: [Codes of Practice for Police Officers in England and Wales, instanceOf, policing code of practice]
-
A.
policing strategy
A policing strategy is a coordinated approach that guides how law enforcement allocates resources, engages with communities, and uses tactics to prevent crime, maintain order, and enhance public safety.
-
B.
police law
Police law is the body of legal rules and principles that governs the organization, powers, duties, and limitations of law enforcement authorities in maintaining public order and safety.
-
C.
press code of practice
A press code of practice is a set of ethical and professional guidelines that regulate the conduct, accuracy, and accountability of journalists and news organizations.
-
D.
policing support entity
A policing support entity is an organization or unit that assists law enforcement agencies by providing specialized services, resources, or expertise to enhance public safety and policing effectiveness.
-
E.
civilian policing role
A civilian policing role is a non-sworn position within a law enforcement or public safety agency that supports policing functions—such as administration, analysis, community outreach, or technical services—without exercising arrest powers or carrying firearms.
- F. None of above. chosen
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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:54 p.m.