Triple
T19958367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Police and Criminal Evidence Act 1984 |
E479744
|
entity |
| Predicate | CodeGRegulates |
P63691
|
FINISHED |
| Object | statutory power 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 power of arrest | Statement: [Police and Criminal Evidence Act 1984, CodeGRegulates, statutory power of arrest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CodeGRegulates Context triple: [Police and Criminal Evidence Act 1984, CodeGRegulates, statutory power of arrest]
-
A.
regulatesProgram
Indicates that one entity exercises control or governance over the operation, rules, or functioning of a program.
-
B.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
C.
regulatesIn
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
-
D.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
E.
regulatesOrImplements
chosen
Indicates that one entity establishes control, guidance, or rules over another entity’s behavior or operation, or carries out and enforces such control or rules in practice.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af2c3548190a44f972a1bd33256 |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.