Triple
T13184397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PacifiCorp |
E313808
|
entity |
| Predicate | emissionSource |
P32799
|
FINISHED |
| Object | greenhouse gas emissions from power generation |
—
|
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: greenhouse gas emissions from power generation | Statement: [PacifiCorp, emissionSource, greenhouse gas emissions from power generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emissionSource Context triple: [PacifiCorp, emissionSource, greenhouse gas emissions from power generation]
-
A.
emissionType
Indicates the specific category or kind of emission associated with an entity or activity.
-
B.
electronSource
Indicates a relationship where one entity serves as the origin or provider of electrons for another entity or process.
-
C.
emitted
Indicates that one entity has released, discharged, or sent out another entity, such as energy, particles, signals, or substances, into its surroundings.
-
D.
sourceCategory
Indicates the classification or type from which something originates or is derived.
-
E.
isMajorSourceOf
chosen
Indicates that one entity serves as a primary or dominant origin, cause, or provider of another entity or effect.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.