Triple
T8908987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specialist Firearms Command |
E212133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Metropolitan Police Service unit |
C3496
|
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: Metropolitan Police Service unit Context triple: [Specialist Firearms Command, instanceOf, Metropolitan Police Service unit]
-
A.
law enforcement unit
chosen
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.
-
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
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.
UK government unit
A UK government unit is an organizational entity within the United Kingdom’s system of public administration that carries out specific governmental functions, services, or policy responsibilities under the authority of a department or minister.
-
E.
organisational unit of the UK Ministry of Defence
An organisational unit of the UK Ministry of Defence is a formally defined structural entity within the department, such as a command, agency, directorate, or division, responsible for specific defence-related functions, resources, and decision-making.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:55 p.m.