Triple
T26807138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coors Light |
E671867
|
entity |
| Predicate | notablePackagingInnovation |
P159208
|
FINISHED |
| Object | cold-activated ink on label |
—
|
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: cold-activated ink on label | Statement: [Coors Light, notablePackagingInnovation, cold-activated ink on label]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePackagingInnovation Context triple: [Coors Light, notablePackagingInnovation, cold-activated ink on label]
-
A.
notablePackagingDesign
Indicates that an entity is recognized for having a distinctive, noteworthy, or otherwise significant packaging design.
-
B.
packagingTechnology
chosen
Indicates the method or technology used to package a product or item.
-
C.
packaging
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
-
D.
notablePackage
Indicates that an entity is a particularly significant, well-known, or otherwise noteworthy package within its domain.
-
E.
commonPackagingFeatures
Indicates that two or more products share the same or very similar packaging characteristics or design elements.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: April 27, 2026, 4:27 a.m.