Triple

T28602904
Position Surface form Disambiguated ID Type / Status
Subject Greater Gabbard Offshore Wind Farm E723960 entity
Predicate nearbyPortUsedDuringConstruction P185943 FINISHED
Object Lowestoft 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: Lowestoft | Statement: [Greater Gabbard Offshore Wind Farm, nearbyPortUsedDuringConstruction, Lowestoft]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nearbyPortUsedDuringConstruction
Context triple: [Greater Gabbard Offshore Wind Farm, nearbyPortUsedDuringConstruction, Lowestoft]
  • A. usedPort
    Indicates that a particular port (such as a network or hardware interface) is or has been utilized by an entity for communication or connection.
  • B. registeredPort
    Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
  • C. usedOnPort
    Indicates that something is applied, connected, or operates specifically on a given port.
  • D. neighboringPort
    Indicates that two ports are geographically close to each other, typically sharing a boundary or lying within a short distance along a coast or waterway.
  • E. hasPortUse
    Indicates that one entity utilizes or is assigned to a particular port for access, communication, or operation.
  • 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_69f01d80b1908190980594837604b8c7 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f7c83f5960819089610ed39c839678 completed May 3, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69f7c475c58c8190a883554231e88c88 completed May 3, 2026, 9:56 p.m.
PDg Predicate description generation batch_69f7c776b4088190bef550c869da530d completed May 3, 2026, 10:08 p.m.
Created at: April 28, 2026, 4:25 a.m.