Triple
T27057840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assam Gas Company |
E684948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | natural gas distribution company |
C1393
|
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: natural gas distribution company Context triple: [Assam Gas Company, instanceOf, natural gas distribution company]
-
A.
natural gas utility
chosen
A natural gas utility is a regulated service provider that supplies, transports, and distributes natural gas to residential, commercial, and industrial customers through an integrated pipeline infrastructure.
-
B.
natural gas storage operator
A natural gas storage operator is an entity responsible for managing facilities that inject, store, and withdraw natural gas to ensure reliable supply, system balance, and market flexibility.
-
C.
liquefied natural gas company
A liquefied natural gas company is an organization that explores, produces, processes, liquefies, transports, and/or markets natural gas in its liquid form for efficient storage and global distribution.
-
D.
industrial gas company
An industrial gas company is a business that produces, stores, and supplies gases such as oxygen, nitrogen, hydrogen, and specialty gases for use in manufacturing, healthcare, energy, and other industrial applications.
-
E.
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.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:19 a.m.