Triple
T8213199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Array |
E191870
|
entity |
| Predicate | singleTurbineCapacity |
P30472
|
FINISHED |
| Object | 3.6 MW |
—
|
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: 3.6 MW | Statement: [London Array, singleTurbineCapacity, 3.6 MW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleTurbineCapacity Context triple: [London Array, singleTurbineCapacity, 3.6 MW]
-
A.
turbineCapacity
chosen
Indicates the power-generating capacity or rated output of a turbine.
-
B.
totalElectricalCapacity_MWe
Indicates the total electrical power generation capacity, measured in megawatts electric (MWe), that an entity can produce or supply.
-
C.
grossElectricalCapacity_MWe
Indicates the total electrical power output capacity of a generating unit, measured in megawatts electric (MWe), before accounting for internal power consumption or losses.
-
D.
windFarmCapacity
Indicates the total power generation capacity of a wind farm, typically measured in units such as megawatts.
-
E.
netElectricalCapacity_MWe
Indicates the relationship specifying an entity’s net electrical power generation capacity, measured in megawatts electric (MWe), after accounting for internal power consumption.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76e1ffa081908883338e7d3a7c6d |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.