Triple
T31480494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burbo Bank Offshore Wind Farm |
E803124
|
entity |
| Predicate | originalWindFarmName |
P202861
|
FINISHED |
| Object | Burbo Bank |
—
|
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: Burbo Bank | Statement: [Burbo Bank Offshore Wind Farm, originalWindFarmName, Burbo Bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalWindFarmName Context triple: [Burbo Bank Offshore Wind Farm, originalWindFarmName, Burbo Bank]
-
A.
hasWindFarm
Indicates that one entity possesses, hosts, or contains a wind farm as part of its assets, infrastructure, or territory.
-
B.
windmillName
Indicates the specific name assigned to a windmill.
-
C.
windFarmType
Indicates the specific category or classification of a wind farm based on its characteristics or configuration.
-
D.
windFarmOperator
Indicates that one entity operates, manages, or is responsible for running a wind farm for another entity or in a given context.
-
E.
windFarmSignificance
Indicates the importance or impact that a wind farm has in a given context, such as energy production, environment, or local economy.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00c8e617548190bba4cdfbb6f512e0 |
completed | May 10, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_6a00c7e816b88190bd40f5ea2a768c8b |
completed | May 10, 2026, 6:01 p.m. |
| PDg | Predicate description generation | batch_6a00c8e566f4819099fead6ead45af09 |
completed | May 10, 2026, 6:05 p.m. |
Created at: April 30, 2026, 9:32 p.m.