Triple
T8213204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Array |
E191870
|
entity |
| Predicate | exportCableVoltage |
P1870
|
FINISHED |
| Object | 150 kV |
—
|
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: 150 kV | Statement: [London Array, exportCableVoltage, 150 kV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportCableVoltage Context triple: [London Array, exportCableVoltage, 150 kV]
-
A.
thirdRailVoltage
Indicates the electrical potential or voltage present on a system’s third rail used for power delivery.
-
B.
signalVoltage
Indicates the electrical potential level carried by a signal in a circuit or communication channel.
-
C.
approximateVoltage
Indicates that one entity represents or provides a value that is close to, but not necessarily exactly equal to, the voltage of another entity.
-
D.
supportsMaximumVoltage
Indicates that an entity is capable of safely operating at or up to a specified maximum voltage level.
-
E.
usesElectricityVoltage
chosen
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76e1ffa081908883338e7d3a7c6d |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.