Triple
T8605200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson Controls |
E203779
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | energy management company |
C15080
|
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 management company Context triple: [Johnson Controls, instanceOf, energy management company]
-
A.
energy management device
An energy management device is a system component that monitors, controls, and optimizes the consumption, storage, and distribution of energy within a defined environment or network.
-
B.
energy solutions company
chosen
An energy solutions company designs, develops, and delivers technologies and services that provide efficient, reliable, and sustainable energy to residential, commercial, and industrial customers.
-
C.
public utility company
A public utility company is an organization, often government-regulated, that provides essential services such as electricity, water, gas, or telecommunications to the public, typically operating as a natural monopoly to ensure reliable and widespread access.
-
D.
energy hub
An energy hub is a centralized system or facility that integrates, converts, stores, and distributes multiple forms of energy (such as electricity, heat, and fuels) to optimize efficiency, reliability, and sustainability across connected users and infrastructures.
-
E.
wholesale energy company
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.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:24 p.m.