Triple
T8487271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapporo Beer |
E200860
|
entity |
| Predicate | packagingDesignFeature |
P39622
|
FINISHED |
| Object | silver can (for many export products) |
—
|
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: silver can (for many export products) | Statement: [Sapporo Beer, packagingDesignFeature, silver can (for many export products)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: packagingDesignFeature Context triple: [Sapporo Beer, packagingDesignFeature, silver can (for many export products)]
-
A.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
brandingFeature
Indicates that one entity serves as a branding-related characteristic, element, or attribute that helps define or distinguish another entity’s brand identity.
-
C.
packagingStyle
chosen
Indicates the manner or format in which a product or item is packaged or presented.
-
D.
packaging
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
-
E.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe556b5188190b1124effd7445803 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.