Triple
T30962441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codes of Practice for Police Officers in England and Wales |
E788864
|
entity |
| Predicate | CodeGDealsWith |
P130364
|
FINISHED |
| Object | statutory powers of arrest |
—
|
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: statutory powers of arrest | Statement: [Codes of Practice for Police Officers in England and Wales, CodeGDealsWith, statutory powers of arrest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CodeGDealsWith Context triple: [Codes of Practice for Police Officers in England and Wales, CodeGDealsWith, statutory powers of arrest]
-
A.
codeOn
Indicates that one entity writes, develops, or modifies software using or for another entity (such as a platform, project, or codebase).
-
B.
PaulOffers
Indicates that Paul presents or proposes something (such as help, goods, or an opportunity) to another party for their consideration or acceptance.
-
C.
bargainsFor
Indicates that one entity negotiates or seeks to obtain another entity, typically aiming for more favorable terms or conditions.
-
D.
section2DealsWith
chosen
Indicates that the second section of a document or text addresses, covers, or is concerned with a specified topic or subject.
-
E.
designCode
Indicates that one entity creates, specifies, or defines the design or coding scheme used by another entity.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:54 p.m.