Triple
T26893700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assam Oil Company |
E677845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | petroleum exploration and production company |
C35950
|
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: petroleum exploration and production company Context triple: [Assam Oil Company, instanceOf, petroleum exploration and production company]
-
A.
exploration and production company
chosen
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.
-
B.
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.
-
C.
oil and gas services company
An oil and gas services company provides specialized technical, operational, and logistical support to exploration and production firms across the hydrocarbon value chain.
-
D.
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.
-
E.
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.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:46 a.m.