Triple
T32959969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horns Rev offshore wind projects |
E843207
|
entity |
| Predicate | distanceFromShoreRange |
P15760
|
FINISHED |
| Object | 14–34 kilometres |
—
|
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: 14–34 kilometres | Statement: [Horns Rev offshore wind projects, distanceFromShoreRange, 14–34 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromShoreRange Context triple: [Horns Rev offshore wind projects, distanceFromShoreRange, 14–34 kilometres]
-
A.
distanceFromCoast
chosen
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
B.
hasMaximumDistanceFromCoast
Indicates that an entity is located at the greatest possible distance from any coastline within a specified area or context.
-
C.
distanceToLand’sEnd
Indicates the measured distance between a given location or object and the specific place referred to as Land’s End.
-
D.
distanceFromInnerIslands
Indicates the measured spatial separation between something and the inner islands.
-
E.
visibilityFromShore
Indicates that something can be seen or is visually detectable from the shoreline or coast.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:21 a.m.