Triple
T28379219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coryton terminal |
E718844
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fuel storage facility |
C18809
|
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: fuel storage facility Context triple: [Coryton terminal, instanceOf, fuel storage facility]
-
A.
petroleum storage facility
chosen
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.
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.
-
D.
industrial storage facility
An industrial storage facility is a large, purpose-built structure designed to securely house, organize, and manage bulk materials, goods, or equipment used in manufacturing, logistics, or distribution operations.
-
E.
spent nuclear fuel storage basin
A spent nuclear fuel storage basin is a heavily shielded, water-filled pool designed to temporarily store and cool irradiated nuclear fuel assemblies while providing radiation protection and containment.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:05 a.m.