Triple
T31004544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essar Oil UK |
E790032
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | downstream oil company |
C49181
|
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: downstream oil company Context triple: [Essar Oil UK, instanceOf, downstream oil company]
-
A.
downstream energy company
chosen
A downstream energy company focuses on refining crude oil, processing natural gas, and marketing and distributing finished petroleum products such as gasoline, diesel, and jet fuel to end consumers and businesses.
-
B.
exploration and production company
An exploration and production company is a business entity that locates, drills, and extracts oil and natural gas resources from underground reservoirs for commercial sale.
-
C.
petroleum holding company
A petroleum holding company is a corporate entity that owns controlling interests in one or more petroleum-related businesses—such as exploration, production, refining, or distribution firms—primarily to manage investments, consolidate control, and optimize financial and strategic decision-making across the portfolio.
-
D.
refining company
A refining company is a business entity that processes raw materials, such as crude oil or metals, into more valuable, usable products through industrial refining operations.
-
E.
oil sands company
An oil sands company is a business entity that explores, extracts, processes, and markets bitumen and heavy oil from oil sands deposits, often integrating mining, upgrading, and environmental management operations.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:57 p.m.