Triple
T30610426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North West CPS Area |
E779163
|
entity |
| Predicate | coversFunction |
P180805
|
FINISHED |
| Object | criminal prosecutions |
—
|
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: criminal prosecutions | Statement: [North West CPS Area, coversFunction, criminal prosecutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversFunction Context triple: [North West CPS Area, coversFunction, criminal prosecutions]
-
A.
coversInterface
Indicates that one entity provides or implements the functionality defined by a specified interface.
-
B.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
C.
coversFully
Indicates that one entity completely and without gaps encloses, spans, or occupies the extent of another entity.
-
D.
coversTo
Indicates that one entity extends its coverage or protective scope to include another entity.
-
E.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
- F. None of above. chosen
Provenance (4 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 29, 2026, 8:26 p.m.