Triple
T35783653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grampian Police |
E1034502
|
entity |
| Predicate | policedTransport |
P60045
|
FINISHED |
| Object | roads in Grampian region |
—
|
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: roads in Grampian region | Statement: [Grampian Police, policedTransport, roads in Grampian region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policedTransport Context triple: [Grampian Police, policedTransport, roads in Grampian region]
-
A.
policesModeOfTransport
chosen
Indicates that an authority or entity enforces rules, regulations, or oversight concerning a particular mode of transport.
-
B.
policeControl
Indicates that one entity exercises authoritative oversight, regulation, or enforcement power over another, as a police force does over people or areas under its jurisdiction.
-
C.
policeUnit
Indicates that one entity is a police unit (such as a department, squad, or division) associated with or responsible for another entity.
-
D.
patrolType
Indicates the specific kind or category of patrol activity being carried out or assigned.
-
E.
policedPort
Indicates that an authority or enforcement entity monitors, regulates, or controls activities at a particular port.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:06 p.m.