Triple
T29941523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNG Canada |
E760510
|
entity |
| Predicate | feedGasSourceRegion |
P410
|
FINISHED |
| Object | Western Canada Sedimentary Basin |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Western Canada Sedimentary Basin | Statement: [LNG Canada, feedGasSourceRegion, Western Canada Sedimentary Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feedGasSourceRegion Context triple: [LNG Canada, feedGasSourceRegion, Western Canada Sedimentary Basin]
-
A.
feedGasSource
Indicates that one entity serves as the supplying source of gas that is fed into another entity or process.
-
B.
gasSource
Indicates that one entity serves as the origin or provider of gas for another entity or process.
-
C.
sourceRegion
chosen
Indicates the geographic or spatial region from which something originates or is derived.
-
D.
isGasRich
Indicates that an entity possesses a relatively high abundance or concentration of gas compared to a defined reference or threshold.
-
E.
keyGasField
Indicates that the subject is a primary or strategically important gas field in relation to the object (such as a region, company, or project).
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69f6780791108190bfec07f0d7119674 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:22 p.m.