Triple
T29941501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNG Canada |
E760510
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | liquefied natural gas export terminal project |
C34880
|
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: liquefied natural gas export terminal project Context triple: [LNG Canada, instanceOf, liquefied natural gas export terminal project]
-
A.
liquefied natural gas project
chosen
A liquefied natural gas project is a large-scale industrial development that encompasses the extraction, processing, liquefaction, storage, and transportation infrastructure required to produce and export natural gas in liquid form.
-
B.
petrochemical export terminal
A petrochemical export terminal is a specialized industrial facility where processed petroleum-based products are stored, handled, and loaded onto ships or other transport modes for international distribution.
-
C.
natural gas terminal
A natural gas terminal is a specialized facility where natural gas is received, stored, processed (such as liquefied or regasified), and transferred between pipelines, ships, or other transport systems for distribution and export.
-
D.
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.
-
E.
wood pellet export terminal
A wood pellet export terminal is a specialized port facility designed for the receipt, storage, handling, and loading of wood pellets onto ships for international transport.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:22 p.m.