Triple
T15238414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaysia LNG complex in Bintulu |
E364189
|
entity |
| Predicate | exportTerminalFor |
P43356
|
FINISHED |
| Object | liquefied natural gas |
—
|
LITERAL FINISHED |
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: liquefied natural gas | Statement: [Malaysia LNG complex in Bintulu, exportTerminalFor, liquefied natural gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportTerminalFor Context triple: [Malaysia LNG complex in Bintulu, exportTerminalFor, liquefied natural gas]
-
A.
TerminalEUsedFor
chosen
Indicates that a terminal E is used for a particular purpose, function, or activity.
-
B.
usedTerminal
Indicates that an entity made use of or interacted with a particular terminal or endpoint device.
-
C.
servesTerminal
Indicates that one entity functions as a terminal or endpoint facility that is served or operated by another entity.
-
D.
terminalFunction
Indicates that an entity serves as an endpoint or final functional unit within a larger structure, process, or system.
-
E.
terminal3Use
Indicates that an entity makes use of or operates from terminal 3 (such as a specific terminal in a facility, station, or airport).
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007da7e988190925a9b67b8070bc7 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.