Triple
T34237800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pop-Tarts |
E878379
|
entity |
| Predicate | hasMarketingMedium |
P39891
|
FINISHED |
| Object | television advertising |
—
|
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: television advertising | Statement: [Pop-Tarts, hasMarketingMedium, television advertising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketingMedium Context triple: [Pop-Tarts, hasMarketingMedium, television advertising]
-
A.
hasMarketingCampaign
Indicates that an entity is associated with or utilizes a specific marketing campaign.
-
B.
hasMarketingElement
Indicates that one entity includes, is associated with, or makes use of a particular marketing-related component or feature.
-
C.
hasMarketingChannel
chosen
Indicates that an entity utilizes or is associated with a particular marketing channel for promotion or communication.
-
D.
hasMarketingTarget
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or segment.
-
E.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
Created at: May 1, 2026, 1:56 a.m.