Triple
T2151103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winston (cigarette) |
E47181
|
entity |
| Predicate | hasPackagingForm |
P9900
|
FINISHED |
| Object | soft pack |
—
|
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: soft pack | Statement: [Winston (cigarette), hasPackagingForm, soft pack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPackagingForm Context triple: [Winston (cigarette), hasPackagingForm, soft pack]
-
A.
packaging
chosen
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
-
B.
packagingRequirement
Indicates the specific conditions, standards, or constraints that must be met in how something is packaged.
-
C.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
-
D.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
E.
hasDosageForm
Indicates the specific physical form or presentation in which a drug or medicinal product is supplied or administered (e.g., tablet, injection, cream).
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe4747a0819080e2234f3ea8995f |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.