Triple
T8333983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ExxonMobil (corporate headquarters) |
E195141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ExxonMobil facility |
C23888
|
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: ExxonMobil facility Context triple: [ExxonMobil (corporate headquarters), instanceOf, ExxonMobil facility]
-
A.
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.
-
B.
offshore petroleum export facility
An offshore petroleum export facility is a marine-based installation that receives, stores, and transfers produced oil or gas from offshore fields to tankers or pipelines for transport to onshore markets.
-
C.
crude oil storage facility
A crude oil storage facility is an industrial site designed to safely receive, hold, and dispatch large volumes of unrefined petroleum using tanks, containment systems, and associated transfer infrastructure.
-
D.
General Motors factory
A General Motors factory is a large-scale automotive manufacturing facility where GM designs, assembles, and tests vehicles and related components using industrial machinery, robotics, and human labor.
-
E.
Tennessee Valley Authority facility
A Tennessee Valley Authority facility is any physical installation, plant, dam, office, or infrastructure site owned, operated, or managed by the Tennessee Valley Authority for power generation, environmental stewardship, or regional development.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:57 p.m.