Triple
T35336033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GAIL gas processing facilities (Dibiyapur) |
E1020454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | natural gas processing plant |
C57347
|
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 processing plant Context triple: [GAIL gas processing facilities (Dibiyapur), instanceOf, natural gas processing plant]
-
A.
oil processing facility
An oil processing facility is an industrial complex where crude oil is received, separated, treated, and refined into usable products such as fuels, lubricants, and feedstocks under controlled conditions.
-
B.
gas plant
chosen
A gas plant is an industrial facility that processes raw natural gas to remove impurities and separate it into marketable products such as pipeline-quality gas and natural gas liquids.
-
C.
natural gas storage facility
A natural gas storage facility is an engineered site where natural gas is injected, stored (often in underground formations or large tanks), and withdrawn to balance supply and demand, ensure reliability, and support market operations.
-
D.
natural gas terminal
A natural gas terminal is a specialized facility where natural gas is received, stored, processed (such as liquefied or regasified), and transferred between pipelines, ships, or other transport systems for distribution and export.
-
E.
natural gas field
A natural gas field is a subsurface accumulation of natural gas trapped in porous rock formations, typically exploited through drilling and production infrastructure for commercial energy use.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.