Triple
T5917310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunnahabhain distillery |
E131610
|
entity |
| Predicate | hasPackagingChange |
P39622
|
FINISHED |
| Object | major rebrand in late 2000s |
—
|
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: major rebrand in late 2000s | Statement: [Bunnahabhain distillery, hasPackagingChange, major rebrand in late 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPackagingChange Context triple: [Bunnahabhain distillery, hasPackagingChange, major rebrand in late 2000s]
-
A.
packagingStyle
chosen
Indicates the manner or format in which a product or item is packaged or presented.
-
B.
packaging
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
-
C.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
D.
hasLegalChange
Indicates that an entity has undergone or is associated with a modification in its legal status, rights, obligations, or regulatory conditions.
-
E.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.