Triple
T9410277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wind of the Sea |
E226686
|
entity |
| Predicate | hasFoundationType |
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: [Wind of the Sea, hasFoundationType, monopile foundations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoundationType Context triple: [Wind of the Sea, hasFoundationType, monopile foundations]
-
A.
hasFoundation
Indicates that an entity is supported, established, or based upon a particular foundation or underlying basis.
-
B.
originalFoundationType
Indicates the type or nature of the initial foundational structure or base on which something was first established or built.
-
C.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
D.
foundationType
chosen
Indicates the structural or organizational basis on which something is built, established, or supported.
-
E.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5255e4fc81908bf2f69c9a12ef83 |
completed | April 1, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.