Triple
T31865458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cowley Ridge Wind Farm |
E813437
|
entity |
| Predicate | gridStatus |
P122956
|
FINISHED |
| Object | grid-connected |
—
|
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: grid-connected | Statement: [Cowley Ridge Wind Farm, gridStatus, grid-connected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridStatus Context triple: [Cowley Ridge Wind Farm, gridStatus, grid-connected]
-
A.
gridConnectionStatus
chosen
Indicates whether and how an entity is currently connected to an electrical or energy distribution grid.
-
B.
gridService
Indicates a relationship where an entity provides, manages, or participates in services related to an electrical or utility grid infrastructure.
-
C.
hasGridConnection
Indicates that an entity is connected to an electrical grid, enabling it to receive or supply grid-based power.
-
D.
hasElectrificationStatus
Indicates that an entity possesses a specified type or level of electrification (e.g., electrified, non-electrified, partially electrified).
-
E.
gridFormation
Indicates that entities are arranged in a regular, grid-like pattern with defined rows and columns.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b07340088190a0cd5b1ebecc5424 |
completed | May 3, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:53 p.m.