Triple
T1444722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Source Performance Standards |
E31151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emission standard |
C4305
|
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: emission standard Context triple: [New Source Performance Standards, instanceOf, emission standard]
-
A.
transportation standard
A transportation standard is an agreed-upon set of rules, specifications, and protocols that ensure compatibility, safety, and efficiency across transportation systems, vehicles, and infrastructure.
-
B.
engineering standard
An engineering standard is a documented set of agreed-upon technical criteria, methods, and requirements intended to ensure safety, interoperability, quality, and consistency in engineering design, production, and operation.
-
C.
official standard
chosen
An official standard is an authoritative, formally approved specification or guideline established by a recognized body to ensure consistency, compatibility, and quality across products, services, or processes.
-
D.
port emissions reduction initiative
A port emissions reduction initiative is a coordinated program of policies, technologies, and operational changes designed to lower air pollutants and greenhouse gas emissions from maritime, terminal, and landside activities within and around a port.
-
E.
cement standard
A cement standard is a defined specification or guideline that establishes the required properties, performance criteria, and testing methods for cement to ensure quality, safety, and consistency in construction applications.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 8 p.m.