Triple
T26252053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Crime Team (Essex Police) |
E656618
|
entity |
| Predicate | investigationScale |
P87971
|
FINISHED |
| Object | force-wide |
—
|
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: force-wide | Statement: [Major Crime Team (Essex Police), investigationScale, force-wide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigationScale Context triple: [Major Crime Team (Essex Police), investigationScale, force-wide]
-
A.
investigativeScope
chosen
Indicates the range or extent of subjects, issues, or activities that an investigation is intended to examine or cover.
-
B.
investigatesIn
Indicates that an entity conducts an investigation or inquiry within, or focused on, a particular context, location, or domain.
-
C.
typeOfInvestigation
Indicates the specific kind or category of investigation being conducted or referred to in the relationship.
-
D.
settingOfInvestigation
Indicates the context, environment, or circumstances in which an investigation takes place.
-
E.
investigatedBy
Indicates that an entity is the subject of an investigation carried out 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcb59cc819095eda1b1a4947a19 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 9:07 p.m.