Triple
T2028334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormonde Offshore Wind Farm |
E44459
|
entity |
| Predicate | hasProjectPhase |
P22825
|
FINISHED |
| Object | operational phase |
—
|
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: operational phase | Statement: [Ormonde Offshore Wind Farm, hasProjectPhase, operational phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProjectPhase Context triple: [Ormonde Offshore Wind Farm, hasProjectPhase, operational phase]
-
A.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
B.
programPhase
chosen
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
C.
hasPhaseRelation
Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
-
D.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
E.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
- 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.