Triple
T33991047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiltshire Police |
E871543
|
entity |
| Predicate | policesTown |
P185981
|
FINISHED |
| Object | Salisbury |
—
|
NE NERFINISHED |
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: Salisbury | Statement: [Wiltshire Police, policesTown, Salisbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policesTown Context triple: [Wiltshire Police, policesTown, Salisbury]
-
A.
policesCity
Indicates that one entity is responsible for providing law enforcement or policing services within a particular city.
-
B.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
-
C.
hasPoliceDepartment
Indicates that an entity possesses, is served by, or is administratively associated with a police department.
-
D.
policeBureau
Indicates that an entity functions as or is associated with a police bureau or police department.
-
E.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 1, 2026, 1:50 a.m.