Triple
T28379858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleve Hill substation |
E718860
|
entity |
| Predicate | gridConnectionFor |
P164444
|
FINISHED |
| Object | London Array |
—
|
NE NERFINISHED |
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: London Array | Statement: [Cleve Hill substation, gridConnectionFor, London Array]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridConnectionFor Context triple: [Cleve Hill substation, gridConnectionFor, London Array]
-
A.
gridConnectionPlannedFor
Indicates that a future or intended connection to an electrical (or utility) grid is planned for the referenced entity.
-
B.
gridConnectionAgreementWith
Indicates an agreement establishing the terms and conditions under which one party is connected to another party’s electrical grid.
-
C.
gridInterconnection
Indicates a connection or linkage between electrical grids that allows power exchange or coordinated operation.
-
D.
gridConnectionStatus
Indicates whether and how an entity is currently connected to an electrical or energy distribution grid.
-
E.
hasGridConnection
Indicates that an entity is connected to an electrical grid, enabling it to receive or supply grid-based power.
- F. None of above. chosen
Provenance (4 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cb538448190be1c85c33d6bdd62 |
completed | May 2, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f64bca8574819095e081cbb7e2f369 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 28, 2026, 1:05 a.m.