Triple
T2028316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormonde Offshore Wind Farm |
E44459
|
entity |
| Predicate | substationType |
P27765
|
FINISHED |
| Object | offshore substation |
—
|
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: offshore substation | Statement: [Ormonde Offshore Wind Farm, substationType, offshore substation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: substationType Context triple: [Ormonde Offshore Wind Farm, substationType, offshore substation]
-
A.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
B.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
C.
typeOfInstallation
Indicates the specific kind or category of installation associated with an entity (e.g., how or in what form something is installed).
-
D.
stationType
chosen
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
-
E.
powerplantRole
Indicates that one entity serves in a specific functional or operational role relative to a power plant.
- 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.