Triple
T24259715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folsom Powerhouse State Historic Park |
E604663
|
entity |
| Predicate | powerhouseEnergySource |
P95815
|
FINISHED |
| Object | hydroelectric |
—
|
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: hydroelectric | Statement: [Folsom Powerhouse State Historic Park, powerhouseEnergySource, hydroelectric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerhouseEnergySource Context triple: [Folsom Powerhouse State Historic Park, powerhouseEnergySource, hydroelectric]
-
A.
isMajorSourceOfElectricityFor
Indicates that one entity provides the primary or dominant share of electrical power used by another entity.
-
B.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
C.
sourceOfPower
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
D.
energyHub
Indicates a central entity that collects, manages, and distributes energy or power among connected entities or systems.
-
E.
energyGenerationMechanism
chosen
Indicates the method or process by which energy is produced or generated by an entity.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6592688190a9c6850a2e979858 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.