Triple
T15348435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Stanvac |
E366985
|
entity |
| Predicate | refineryClosureType |
P65693
|
FINISHED |
| Object | mothballed then permanently closed |
—
|
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: mothballed then permanently closed | Statement: [Port Stanvac, refineryClosureType, mothballed then permanently closed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refineryClosureType Context triple: [Port Stanvac, refineryClosureType, mothballed then permanently closed]
-
A.
closureType
chosen
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
B.
subjectToClosure
Indicates that an entity is liable or scheduled to be closed, discontinued, or shut down under certain conditions or plans.
-
C.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
D.
closureReason
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
E.
closedForReconstructionTo
Indicates that access or use of something is prohibited for a party because it is undergoing reconstruction.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e27f8a88190a0f65756e3a1fdfc |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.