Triple
T9841888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport Lights |
E239246
|
entity |
| Predicate | wasMarketedAs |
P21045
|
FINISHED |
| Object | light cigarette |
—
|
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: light cigarette | Statement: [Newport Lights, wasMarketedAs, light cigarette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMarketedAs Context triple: [Newport Lights, wasMarketedAs, light cigarette]
-
A.
marketedFor
Indicates that something is promoted, advertised, or positioned as being intended or suitable for a particular use, audience, or purpose.
-
B.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
-
C.
originalMarketingName
Indicates the original marketing or brand name under which an entity (such as a product or service) was first promoted or sold.
-
D.
alsoSoldAs
chosen
Indicates that one item is marketed or available under an alternative name, label, or product identity.
-
E.
marketedFrom
Indicates that a product, service, or offering began to be marketed starting from a specified time or date.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34e3420819084bb31170e643cd0 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.