Triple
T9120106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Prosecution Service |
E218823
|
entity |
| Predicate | excludesRole |
P3119
|
FINISHED |
| Object | investigating crimes |
—
|
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: investigating crimes | Statement: [Crown Prosecution Service, excludesRole, investigating crimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludesRole Context triple: [Crown Prosecution Service, excludesRole, investigating crimes]
-
A.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
B.
excludes
chosen
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
C.
excludesRegion
Indicates that one entity explicitly omits, leaves out, or does not apply to a specified region or geographic area.
-
D.
excludesAward
Indicates that one entity explicitly omits or disqualifies another entity from receiving a particular award.
-
E.
excludesPhase
Indicates that one entity explicitly omits, leaves out, or does not include a particular phase or stage within a process or lifecycle.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a902e08190a7eb4728f32b9e1d |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.