Triple
T30435329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US EPA light-duty standards |
E774292
|
entity |
| Predicate | dataRequirement |
P18299
|
FINISHED |
| Object | manufacturer fleet emissions data |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: manufacturer fleet emissions data | Statement: [US EPA light-duty standards, dataRequirement, manufacturer fleet emissions data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRequirement Context triple: [US EPA light-duty standards, dataRequirement, manufacturer fleet emissions data]
-
A.
typeOfRequirement
Indicates that one requirement is classified as a specific kind or category of another, more general requirement.
-
B.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
-
C.
projectRequirement
Indicates that one entity specifies a necessary condition, resource, or criterion that must be satisfied for a project associated with another entity.
-
D.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
-
E.
requiresDataAvailability
chosen
Indicates that one entity’s operation, validity, or execution is contingent on the presence, accessibility, or readiness of specific data.
- F. None of above.
Provenance (3 batches)
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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68693d1b481909053505550c07c9d |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:07 p.m.