Triple
T18754969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSNI Roads Policing Unit |
E458625
|
entity |
| Predicate | typeOfPoliceActivity |
P116371
|
FINISHED |
| Object | specialist roads policing |
—
|
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: specialist roads policing | Statement: [PSNI Roads Policing Unit, typeOfPoliceActivity, specialist roads policing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPoliceActivity Context triple: [PSNI Roads Policing Unit, typeOfPoliceActivity, specialist roads policing]
-
A.
typeOfLawEnforcement
Indicates that one entity is a specific kind or category of law enforcement associated with another entity.
-
B.
patrolType
chosen
Indicates the specific kind or category of patrol activity being carried out or assigned.
-
C.
policeDepartmentType
Indicates the specific organizational category or classification of a police department (e.g., municipal, state, federal).
-
D.
officerCategory
Indicates the classification or type of officer role that an individual holds within an organization or system.
-
E.
typeOfPowerExercised
Indicates the specific kind or nature of power or authority that is being exercised in a given relationship or context.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579f084208190a4b3563d47154e69 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.