Triple
T2028296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormonde Offshore Wind Farm |
E44459
|
entity |
| Predicate | usesFoundationType |
P29685
|
FINISHED |
| Object | monopile foundations |
—
|
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: monopile foundations | Statement: [Ormonde Offshore Wind Farm, usesFoundationType, monopile foundations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFoundationType Context triple: [Ormonde Offshore Wind Farm, usesFoundationType, monopile foundations]
-
A.
hasFoundation
Indicates that an entity is supported, established, or based upon a particular foundation or underlying basis.
-
B.
foundationType
chosen
Indicates the structural or organizational basis on which something is built, established, or supported.
-
C.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
adoptedFrameworkType
Indicates that one entity has chosen and is using a particular framework type as its adopted standard or approach.
-
E.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9136f888190b0fd03530e9eda1e |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.