Triple
T24668142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CalGEM |
E610741
|
entity |
| Predicate | typeOfEnergyRegulated |
P5332
|
FINISHED |
| Object | geothermal energy |
—
|
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: geothermal energy | Statement: [CalGEM, typeOfEnergyRegulated, geothermal energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEnergyRegulated Context triple: [CalGEM, typeOfEnergyRegulated, geothermal energy]
-
A.
electricityProviderType
Indicates the specific category or kind of electricity provider associated with an entity.
-
B.
energyType
chosen
Indicates the kind or category of energy associated with an entity or process.
-
C.
energyRegime
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
D.
electricityMarketedBy
Indicates that one entity is responsible for marketing, promoting, or selling electricity provided by another entity.
-
E.
energySystemOperator
Indicates that one entity operates, manages, or controls an energy system on behalf of or in relation to another 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 2:41 a.m.