Triple
T13522789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADNOC Distribution |
E322941
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fuel retail company |
C10744
|
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: fuel retail company Context triple: [ADNOC Distribution, instanceOf, fuel retail company]
-
A.
fuel retailer
chosen
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.
petroleum holding company
A petroleum holding company is a corporate entity that owns controlling interests in one or more petroleum-related businesses—such as exploration, production, refining, or distribution firms—primarily to manage investments, consolidate control, and optimize financial and strategic decision-making across the portfolio.
-
D.
hydrocarbon fuel
A hydrocarbon fuel is a combustible substance composed primarily of hydrogen and carbon atoms that releases energy through oxidation, typically used for heating, power generation, and propulsion.
-
E.
petroleum storage facility
A petroleum storage facility is an industrial site designed for the safe receipt, containment, handling, and distribution of crude oil and refined petroleum products in large tanks and associated 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.