Triple
T9829477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winston Silver |
E238744
|
entity |
| Predicate | belongsToProductCategory |
P15481
|
FINISHED |
| Object | filtered cigarettes |
—
|
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: filtered cigarettes | Statement: [Winston Silver, belongsToProductCategory, filtered cigarettes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToProductCategory Context triple: [Winston Silver, belongsToProductCategory, filtered cigarettes]
-
A.
hasRelatedCategory
Indicates that one category is associated with another category through a non-hierarchical, contextually relevant relationship.
-
B.
belongsToCatalogOf
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
C.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
D.
haveCategoryCode
Indicates that an entity is associated with a specific classification or category identified by a code.
-
E.
belongsToProductLine
Indicates that an item or product is associated with and classified under a specific product line.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3282a2481908913addf2b3fa58b |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.