Triple
T10132731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScottishPower transmission network |
E226777
|
entity |
| Predicate | voltageCategory |
P34711
|
FINISHED |
| Object | extra-high voltage |
—
|
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: extra-high voltage | Statement: [ScottishPower transmission network, voltageCategory, extra-high voltage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voltageCategory Context triple: [ScottishPower transmission network, voltageCategory, extra-high voltage]
-
A.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
B.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
C.
gridVoltageLevel
chosen
Indicates the electrical voltage level at which a power grid or network segment operates.
-
D.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
-
E.
typicalVoltageSpacing
Indicates the usual or standard voltage difference that is maintained or expected between two related electrical points or levels.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd336cbf48190b647c69675d0b06f |
completed | April 2, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:06 p.m.