Triple
T20781091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Ellen Distillery |
E511480
|
entity |
| Predicate | reopeningAnnounced |
P77405
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Port Ellen Distillery, reopeningAnnounced, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopeningAnnounced Context triple: [Port Ellen Distillery, reopeningAnnounced, 2017]
-
A.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
B.
reopeningToPublic
chosen
Indicates that an entity, previously closed or restricted, is being opened again for access or use by the general public.
-
C.
partialReopeningDate
Indicates the date on which an entity is reopened in a limited or partial capacity, rather than fully resuming normal operation.
-
D.
reopeningAs
Indicates that an entity that was previously closed or inactive is starting operations again under a new or updated form, identity, or function.
-
E.
reopeningPlan
Indicates that there is a planned or scheduled process for resuming operations or activities after a closure or interruption.
- 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.