Triple
T21014780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dewsbury Borough Police |
E517643
|
entity |
| Predicate | policeForceLevel |
P33005
|
FINISHED |
| Object | borough level |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: borough level | Statement: [Dewsbury Borough Police, policeForceLevel, borough level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeForceLevel Context triple: [Dewsbury Borough Police, policeForceLevel, borough level]
-
A.
lawEnforcementLevel
chosen
Indicates the degree or intensity of law enforcement presence, activity, or strictness applied in a given context.
-
B.
policeForceCharacteristic
Indicates that a specified characteristic, quality, or attribute is associated with a particular police force.
-
C.
policeRank
Indicates that one entity holds a specific rank or position within a police organization relative to another entity.
-
D.
policePresence
Indicates that law enforcement officers are present at or monitoring a particular location, event, or situation.
-
E.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
- F. None of above.
Provenance (3 batches)
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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5764188190829de6f5abd6e00f |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.