Triple
T26814733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakota Access Pipeline |
E672094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crude oil pipeline |
C17374
|
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: crude oil pipeline Context triple: [Dakota Access Pipeline, instanceOf, crude oil pipeline]
-
A.
crude oil pipeline system
chosen
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.
interstate pipeline
An interstate pipeline is a large-scale transportation system of pipes and related facilities that moves natural gas, oil, or other fluids across state boundaries under federal regulation.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 4:31 a.m.