Triple
T36034217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strathclyde Police |
E1042352
|
entity |
| Predicate | policedUrbanArea |
P191611
|
FINISHED |
| Object | Greater Glasgow conurbation |
—
|
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: Greater Glasgow conurbation | Statement: [Strathclyde Police, policedUrbanArea, Greater Glasgow conurbation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policedUrbanArea Context triple: [Strathclyde Police, policedUrbanArea, Greater Glasgow conurbation]
-
A.
policeAndCrimeCommissionerArea
Indicates the geographic area over which a specific Police and Crime Commissioner has authority or jurisdiction.
-
B.
policesMetropolitanBorough
Indicates that an entity is responsible for providing policing services to a specified metropolitan borough.
-
C.
isUrbanConstituency
Indicates that a given constituency is classified as urban rather than rural or semi-urban.
-
D.
localAuthorityArea
Indicates that one entity is a geographic or administrative area governed or managed by a specified local authority.
-
E.
localGovernmentAreaReorganised
Indicates that a local government area has undergone an official administrative reorganization, such as boundary changes, mergers, or splits.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.