Triple
T19040864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alyeska Pipeline Service Company |
E465996
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | oil pipeline company |
C32595
|
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: oil pipeline company Context triple: [Alyeska Pipeline Service Company, instanceOf, oil pipeline company]
-
A.
crude oil pipeline system
A crude oil pipeline system is an integrated network of pipes, pumps, valves, and control equipment designed to safely and efficiently transport unrefined petroleum from production sites to storage, processing, or export facilities.
-
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.
energy infrastructure company
chosen
An energy infrastructure company develops, owns, and operates the physical assets and networks that produce, transport, store, and deliver energy resources and power to end users.
-
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.
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.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.