Triple
T25664440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copenhagen |
E643472
|
entity |
| Predicate | advertisedAs |
P158966
|
FINISHED |
| Object | premium smokeless tobacco |
—
|
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: premium smokeless tobacco | Statement: [Copenhagen, advertisedAs, premium smokeless tobacco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advertisedAs Context triple: [Copenhagen, advertisedAs, premium smokeless tobacco]
-
A.
advertisedUsing
Indicates that something is promoted or made known through a particular medium, method, or channel of advertising.
-
B.
advertises
Indicates that one entity promotes, publicizes, or markets another entity, typically to attract attention or customers.
-
C.
announcedAs
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by another entity.
-
D.
adType
Indicates the classification or category of an advertisement associated with an entity or event.
-
E.
manufacturerPromoted
Indicates that a manufacturer has actively advertised, endorsed, or otherwise promoted a product, service, or entity.
- F. None of above. chosen
Provenance (4 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faf1f9c48190ad732234e836b143 |
completed | May 2, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 7 p.m.