Triple
T16505338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oglethorpe Power Corporation |
E400911
|
entity |
| Predicate | energySourcePortfolioIncludes |
P110422
|
FINISHED |
| Object | nuclear power |
—
|
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: nuclear power | Statement: [Oglethorpe Power Corporation, energySourcePortfolioIncludes, nuclear power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energySourcePortfolioIncludes Context triple: [Oglethorpe Power Corporation, energySourcePortfolioIncludes, nuclear power]
-
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.
primaryFuelMixIncludes
chosen
Indicates that a primary fuel mixture contains or incorporates a specified fuel component as one of its constituent parts.
-
D.
includesPowerGeneration
Indicates that an entity encompasses or involves facilities, systems, or activities related to generating electrical or other forms of power.
-
E.
energyGenerationMechanism
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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e51ce1c81909548298f703a7ffa |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.