Triple
T9297850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JP-7 |
E223685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hydrocarbon fuel |
C27160
|
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: hydrocarbon fuel Context triple: [JP-7, instanceOf, hydrocarbon fuel]
-
A.
fuel retailer
A fuel retailer is a business entity that purchases fuel products from suppliers and sells them to end consumers, typically through service stations or forecourts, often providing related services such as convenience retail and vehicle amenities.
-
B.
gasoline brand
A gasoline brand is a marketed identity under which fuel products are sold, encompassing specific formulations, quality standards, and associated services offered by a petroleum company.
-
C.
low‑carbon fuel project
A low‑carbon fuel project is an initiative that develops, produces, or deploys fuels with significantly reduced lifecycle greenhouse gas emissions compared to conventional fossil fuels, often involving advanced technologies, sustainable feedstocks, and emissions monitoring to support climate and energy transition goals.
-
D.
liquid-fueled rocket
A liquid-fueled rocket is a propulsion system that burns liquid propellants—typically a fuel and an oxidizer stored in separate tanks—to produce high-velocity exhaust and generate thrust.
-
E.
liquid-fueled rocket engine
A liquid-fueled rocket engine is a propulsion system that burns liquid propellants—typically a fuel and an oxidizer—pumped into a combustion chamber to produce high-velocity exhaust for thrust.
- F. None of above. chosen
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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:36 p.m.