Triple
T29941536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNG Canada |
E760510
|
entity |
| Predicate | exportDestinationRegion |
P83648
|
FINISHED |
| Object | East Asia |
—
|
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: East Asia | Statement: [LNG Canada, exportDestinationRegion, East Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportDestinationRegion Context triple: [LNG Canada, exportDestinationRegion, East Asia]
-
A.
hasDestinationRegion
chosen
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
-
B.
transferDestination
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
-
C.
sampleDestination
Indicates that something serves as, or is designated to be, the target location or endpoint for a sample.
-
D.
originalDestination
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
-
E.
isRegionalDestination
Indicates that a place serves as a primary travel or attraction target within a specific geographic region.
- 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.