Triple
T28472193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunfleet Sands Offshore Wind Farm |
E720467
|
entity |
| Predicate | distanceToNearestPort |
P201677
|
FINISHED |
| Object | near Harwich and Clacton ports |
—
|
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: near Harwich and Clacton ports | Statement: [Gunfleet Sands Offshore Wind Farm, distanceToNearestPort, near Harwich and Clacton ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNearestPort Context triple: [Gunfleet Sands Offshore Wind Farm, distanceToNearestPort, near Harwich and Clacton ports]
-
A.
nearestMajorPort
Indicates the closest significant seaport to a given location or entity, typically based on geographic distance.
-
B.
nearbyCityOrPort
Indicates that one location is geographically close to a city or port, typically within a short travel distance.
-
C.
nearbyPortFacility
Indicates that one entity is located close to or in the immediate vicinity of a port facility.
-
D.
nearestPointTo
Indicates the point that is closest in distance to a given reference point or object among a set of candidates.
-
E.
distanceToLowestoft
Indicates the spatial distance between a given entity and the location of Lowestoft.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
| PDg | Predicate description generation | batch_6a001440a26c81908ba50779bb6e1679 |
completed | May 10, 2026, 5:14 a.m. |
Created at: April 28, 2026, 2:49 a.m.