Triple
T17596862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hetch Hetchy Power System |
E428593
|
entity |
| Predicate | transmissionVoltageLevel |
P34711
|
FINISHED |
| Object | 115 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: 115 kV | Statement: [Hetch Hetchy Power System, transmissionVoltageLevel, 115 kV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionVoltageLevel Context triple: [Hetch Hetchy Power System, transmissionVoltageLevel, 115 kV]
-
A.
gridVoltageLevel
chosen
Indicates the electrical voltage level at which a power grid or network segment operates.
-
B.
overheadLineVoltage
Indicates the voltage level carried by an overhead power line in the relationship.
-
C.
plannedTransmissionLineLength
Indicates the intended or projected length of a transmission line as specified in a plan or design.
-
D.
electrificationTerminusOf
Indicates that a location or point serves as the end of an electrified section of a route, line, or network.
-
E.
usesElectricityVoltage
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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469ec335c8190abcaff700cfff23b |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.