Triple
T2046361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Hoyle Offshore Wind Farm |
E45460
|
entity |
| Predicate | hasBladeCountPerTurbine |
P36030
|
FINISHED |
| Object | 3 |
—
|
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 | Statement: [North Hoyle Offshore Wind Farm, hasBladeCountPerTurbine, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBladeCountPerTurbine Context triple: [North Hoyle Offshore Wind Farm, hasBladeCountPerTurbine, 3]
-
A.
numberOfTurbines
Indicates the quantity of turbines associated with a given entity or installation.
-
B.
hasTurbines
Indicates that one entity is equipped with, contains, or includes one or more turbines in relation to another entity.
-
C.
tailRotorBlades
Indicates the relationship in which an entity functions as the rotor blades located at the tail of a rotorcraft, used for stability and directional control.
-
D.
mainRotorBlades
Indicates the relationship between a helicopter’s main rotor assembly and the blades that are attached to and rotate as part of that primary lifting rotor system.
-
E.
typicalSpindleCount
Indicates the usual or standard number of spindles associated with an entity in this relationship.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abbc2b07d48190ba9d67353167b472 |
completed | March 7, 2026, 5:48 a.m. |
Created at: March 4, 2026, 7:39 p.m.