Triple
T17078351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koch Supply & Trading |
E414407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | energy trading company |
C14746
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: energy trading company Context triple: [Koch Supply & Trading, instanceOf, energy trading company]
-
A.
wholesale energy company
chosen
A wholesale energy company is a business that buys large quantities of electricity or fuel from producers and sells them in bulk to utilities, large industrial customers, or other resellers, often managing supply, pricing, and risk in energy markets.
-
B.
integrated energy company
An integrated energy company is a business that operates across multiple stages of the energy value chain—such as exploration, production, refining, distribution, and retail—often spanning both fossil fuels and renewable energy sources.
-
C.
energy supplier
An energy supplier is an entity that procures, manages, and delivers electricity and/or gas to consumers, handling contracts, billing, and customer service while interfacing with energy producers and grid operators.
-
D.
energy infrastructure company
An energy infrastructure company develops, owns, and operates the physical assets and networks that produce, transport, store, and deliver energy resources and power to end users.
-
E.
energy trading software platform
An energy trading software platform is a digital system that enables market participants to analyze prices, manage positions, execute and settle trades, and monitor risk across power, gas, and other energy markets.
- F. None of above.
Provenance (1 batch)
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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:34 a.m.