Triple
T35632150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yadana gas project |
E1029616
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gas pipeline project |
C62470
|
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: gas pipeline project Context triple: [Yadana gas project, instanceOf, gas pipeline project]
-
A.
liquefied natural gas project
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.
interstate pipeline
An interstate pipeline is a large-scale transportation system of pipes and related facilities that moves natural gas, oil, or other fluids across state boundaries under federal regulation.
-
C.
government infrastructure pipeline
A government infrastructure pipeline is a structured, long-term sequence of planned, funded, and prioritized public works projects—such as transportation, utilities, and civic facilities—designed to guide investment, development, and maintenance of essential national or regional infrastructure.
-
D.
crude oil pipeline system
A crude oil pipeline system is an integrated network of pipes, pumps, valves, and control equipment designed to safely and efficiently transport unrefined petroleum from production sites to storage, processing, or export facilities.
-
E.
gas plant
A gas plant is an industrial facility that processes raw natural gas to remove impurities and separate it into marketable products such as pipeline-quality gas and natural gas liquids.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.