Triple
T22137012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAPS Authorization Act |
E547055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pipeline regulation law |
C18939
|
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 regulation law Context triple: [TAPS Authorization Act, instanceOf, pipeline regulation law]
-
A.
pipeline legislation
chosen
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.
economic regulation
Economic regulation is the set of laws, rules, and administrative actions through which governments influence, control, or guide economic activity, markets, and business behavior to achieve public policy objectives.
-
D.
regulations
Regulations are authoritative rules or directives established by a governing body to control, manage, or guide behaviors and processes within a specific domain.
-
E.
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.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:32 p.m.