Triple
T22229849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryan Mound site |
E549436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Strategic Petroleum Reserve storage site |
C18808
|
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: Strategic Petroleum Reserve storage site Context triple: [Bryan Mound site, instanceOf, Strategic Petroleum Reserve storage site]
-
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
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.
ExxonMobil facility
An ExxonMobil facility is a physical site owned or operated by ExxonMobil where petroleum, natural gas, or related chemical products are explored, produced, processed, stored, or distributed.
-
D.
national oil reserve
chosen
A national oil reserve is a government-controlled stockpile of crude oil maintained to ensure energy security, stabilize supply during disruptions, and support economic and strategic interests.
-
E.
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.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:37 p.m.