Triple
T25464723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In-Use Off-Road Diesel-Fueled Fleets Regulation |
E638142
|
entity |
| Predicate | fuelTypeRegulated |
P159129
|
FINISHED |
| Object | diesel fuel |
—
|
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: diesel fuel | Statement: [In-Use Off-Road Diesel-Fueled Fleets Regulation, fuelTypeRegulated, diesel fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelTypeRegulated Context triple: [In-Use Off-Road Diesel-Fueled Fleets Regulation, fuelTypeRegulated, diesel fuel]
-
A.
fuelTypeLicensed
Indicates that an entity is authorized or licensed to use, supply, or handle a specified type of fuel.
-
B.
fuelTypeSupported
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
-
C.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
D.
laterFuelType
Indicates that one fuel type is used or adopted after another fuel type in time.
-
E.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
- F. None of above. chosen
Provenance (4 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72f1a788190904ed62ebdccc57c |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 2:14 p.m.