Triple
T16000994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckeye Pipe Line Company |
E388090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pipeline company |
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: pipeline company Context triple: [Buckeye Pipe Line Company, instanceOf, pipeline company]
-
A.
pipeline legislation
Pipeline legislation is a body of laws and regulations that govern the planning, approval, construction, operation, and decommissioning of pipelines to ensure safety, environmental protection, and fair access.
-
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 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.
-
D.
government infrastructure pipeline
A government infrastructure pipeline is a structured, long-term sequence of planned, funded, and prioritized public works projects—such as transportation, utilities, and civic facilities—designed to guide investment, development, and maintenance of essential national or regional infrastructure.
-
E.
piping standard
A piping standard is a formal specification that defines the materials, dimensions, design, fabrication, testing, and installation requirements for piping systems to ensure safety, compatibility, and performance.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:55 a.m.