Triple
T15285043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jefferson County industrial corridor |
E365371
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | petrochemical corridor |
C2952
|
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: petrochemical corridor Context triple: [Jefferson County industrial corridor, instanceOf, petrochemical corridor]
-
A.
petrochemical export terminal
A petrochemical export terminal is a specialized industrial facility where processed petroleum-based products are stored, handled, and loaded onto ships or other transport modes for international distribution.
-
B.
coastal industrial area
A coastal industrial area is a shoreline zone dominated by factories, ports, warehouses, and related infrastructure that support manufacturing, shipping, and other large-scale economic activities.
-
C.
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.
-
D.
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.
-
E.
transport corridor
chosen
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:15 a.m.