Triple
T11986445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwestern Power Administration |
E285290
|
entity |
| Predicate | usesTransmissionVoltageLevel |
P34711
|
FINISHED |
| Object | 69 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: 69 kV | Statement: [Southwestern Power Administration, usesTransmissionVoltageLevel, 69 kV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTransmissionVoltageLevel Context triple: [Southwestern Power Administration, usesTransmissionVoltageLevel, 69 kV]
-
A.
gridVoltageLevel
chosen
Indicates the electrical voltage level at which a power grid or network segment operates.
-
B.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
C.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
D.
operatesTransmissionLines
Indicates that one entity manages and controls the functioning of electrical transmission lines associated with another entity.
-
E.
powerTransmissionUse
Indicates that one entity uses another as a means or medium for transmitting power.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.