Triple
T33991046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiltshire Police |
E871543
|
entity |
| Predicate | policesRuralArea |
P125179
|
FINISHED |
| Object | Salisbury Plain |
—
|
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 Plain | Statement: [Wiltshire Police, policesRuralArea, Salisbury Plain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policesRuralArea Context triple: [Wiltshire Police, policesRuralArea, Salisbury Plain]
-
A.
policesRuralAreas
chosen
Indicates that an entity is responsible for enforcing law and maintaining public order in rural or non-urban areas.
-
B.
governsRuralArea
Indicates that one entity has governing authority or administrative control over a rural area associated with another entity.
-
C.
areaTypePoliced
Indicates that a particular type of geographic or administrative area falls under the policing responsibility or jurisdiction of a specified policing entity.
-
D.
policeServices
Indicates that one entity provides or is responsible for law enforcement or policing services to another entity or within a specified area.
-
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.
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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:50 a.m.