Triple
T28439903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire Electricity Board |
E715677
|
entity |
| Predicate | distributionVoltageRange |
P34711
|
FINISHED |
| Object | low 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: low voltage | Statement: [Yorkshire Electricity Board, distributionVoltageRange, low voltage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributionVoltageRange Context triple: [Yorkshire Electricity Board, distributionVoltageRange, low voltage]
-
A.
typicalVoltageRange
Indicates the usual minimum-to-maximum voltage interval within which something is designed or expected to operate.
-
B.
gridVoltageLevel
chosen
Indicates the electrical voltage level at which a power grid or network segment operates.
-
C.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
D.
typicalElectricalOutputRange
Indicates the usual range of electrical power or energy output that an entity is expected to produce under normal operating conditions.
-
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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 1:45 a.m.