Triple
T15243136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cushing, Oklahoma |
E364309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | oil storage hub |
C18810
|
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 storage hub Context triple: [Cushing, Oklahoma, instanceOf, oil storage hub]
-
A.
petroleum storage facility
A petroleum storage facility is an industrial site designed for the safe receipt, containment, handling, and distribution of crude oil and refined petroleum products in large tanks and associated infrastructure.
-
B.
crude oil storage facility
chosen
A crude oil storage facility is an industrial site designed to safely receive, hold, and dispatch large volumes of unrefined petroleum using tanks, containment systems, and associated transfer infrastructure.
-
C.
oil and gas logistics hub
A strategically located facility that coordinates the transportation, storage, handling, and distribution of oil and gas products across pipelines, marine, rail, and road networks to optimize supply chain efficiency and reliability.
-
D.
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.
-
E.
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.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.