Triple
T35783632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grampian Police |
E1034502
|
entity |
| Predicate | policedPort |
P189483
|
FINISHED |
| Object | Aberdeen Harbour |
—
|
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: Aberdeen Harbour | Statement: [Grampian Police, policedPort, Aberdeen Harbour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policedPort Context triple: [Grampian Police, policedPort, Aberdeen Harbour]
-
A.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port of another entity.
-
B.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
-
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.
portCaptured
Indicates that control of a port has been seized or taken over by a particular party or force.
-
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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:06 p.m.