Triple
T9072298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westview Wood Pellet Terminal |
E217396
|
entity |
| Predicate | exportMode |
P86797
|
FINISHED |
| Object | deep-sea vessels |
—
|
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: deep-sea vessels | Statement: [Westview Wood Pellet Terminal, exportMode, deep-sea vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportMode Context triple: [Westview Wood Pellet Terminal, exportMode, deep-sea vessels]
-
A.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
-
B.
alternateMode
Indicates that one entity functions as an alternative form, configuration, or mode of operation for another entity.
-
C.
originalMode
Indicates that something preserves, reflects, or is associated with its initial or default mode of operation or state.
-
D.
recommendedMode
Indicates that one entity is suggested or advised as the preferred mode, method, or way of doing or experiencing something in relation to another entity.
-
E.
usedOnMode
Indicates that something is applied, operated, or functions specifically in a given mode or operational setting.
- F. None of above. chosen
Provenance (4 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ffa04819086be5763133c5067 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc668ad3d881908a8a93a6a1d553e4 |
completed | April 1, 2026, 12:27 a.m. |
Created at: March 30, 2026, 7:12 p.m.