Triple
T36034203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strathclyde Police |
E1042352
|
entity |
| Predicate | policeAreaCode |
P191396
|
FINISHED |
| Object | Strathclyde |
—
|
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: Strathclyde | Statement: [Strathclyde Police, policeAreaCode, Strathclyde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeAreaCode Context triple: [Strathclyde Police, policeAreaCode, Strathclyde]
-
A.
policeNumber
Indicates that an entity is associated with a specific police-related identification or reference number.
-
B.
policeNumberingSystem
Indicates a system by which police assign and manage identification numbers to cases, incidents, or personnel.
-
C.
policeAreaPrecursorOf
Indicates that one police area served as a predecessor or earlier form of another police area in an administrative or organizational sequence.
-
D.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
-
E.
hasAreaCode
Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
- 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_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:07 p.m.