Triple
T34108983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedfordshire Police |
E874785
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | police force of England and Wales |
C3345
|
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: police force of England and Wales Context triple: [Bedfordshire Police, instanceOf, police force of England and Wales]
-
A.
British paramilitary police force
A British paramilitary police force is a law enforcement body organized, trained, and equipped along military lines to perform policing, public order, and security duties while operating under civilian authority.
-
B.
British police officer
A British police officer is a sworn law enforcement official in the United Kingdom responsible for maintaining public order, preventing and investigating crime, and protecting the public in accordance with UK law and policing standards.
-
C.
police force
chosen
A police force is an organized body of officers empowered by a government to maintain public order, enforce laws, prevent and investigate crime, and protect citizens and property.
-
D.
government agency of the United Kingdom
A government agency of the United Kingdom is an official public body established by the UK government to carry out specific administrative, regulatory, or service-delivery functions on its behalf.
-
E.
public office in England and Wales
A public office in England and Wales is a position conferred by the state or a public authority that carries ongoing duties to the public, is created or recognized by law, and involves the exercise of public functions or powers.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:53 a.m.