Triple
T20781092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Ellen Distillery |
E511480
|
entity |
| Predicate | plannedRestartOfProduction |
P26282
|
FINISHED |
| Object | 2020s |
—
|
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: 2020s | Statement: [Port Ellen Distillery, plannedRestartOfProduction, 2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedRestartOfProduction Context triple: [Port Ellen Distillery, plannedRestartOfProduction, 2020s]
-
A.
restartedFullProductionIn
Indicates that an entity resumed operating at full production capacity starting at a specified time or in a specified period.
-
B.
plannedReplacement
Indicates that one entity is intended or scheduled to be replaced by another entity in the future.
-
C.
relatedRestart
Indicates that one process, event, or state is connected to or causes the restarting of another process, event, or state.
-
D.
plannedProductionVersion
Indicates that a specific version of a product or item is scheduled or intended to be produced in the future.
-
E.
plannedAt
chosen
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c287b5288190823766fe59402d48 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.