Triple
T10132749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Kingdom offshore wind sector |
E226778
|
entity |
| Predicate | electricityType |
P21522
|
FINISHED |
| Object | renewable electricity |
—
|
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: renewable electricity | Statement: [United Kingdom offshore wind sector, electricityType, renewable electricity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricityType Context triple: [United Kingdom offshore wind sector, electricityType, renewable electricity]
-
A.
typeOfElectricity
chosen
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
B.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
C.
electricityMarketedBy
Indicates that one entity is responsible for marketing, promoting, or selling electricity provided by another entity.
-
D.
electricityUse
Indicates the amount or pattern of electrical energy consumed by an entity during a specified period or activity.
-
E.
electrificationUsedFor
Indicates that electrification is employed as a means or method to achieve, enable, or support a particular function, process, or purpose.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd336cbf48190b647c69675d0b06f |
completed | April 2, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:06 p.m.