Triple
T29372569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nike advertising campaigns |
E744892
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | advertising campaign series |
C7298
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: advertising campaign series Context triple: [Nike advertising campaigns, instanceOf, advertising campaign series]
-
A.
print advertisement series
A print advertisement series is a coordinated set of related print ads that share a common theme, visual style, and messaging strategy to promote a product, service, or brand across multiple placements and time periods.
-
B.
television advertising campaign
A television advertising campaign is a coordinated series of TV commercials and related promotional activities designed to communicate a specific message to a target audience over a defined period to achieve marketing objectives.
-
C.
marketing campaign
chosen
A marketing campaign is a coordinated series of promotional activities and messages designed to achieve specific business objectives with a defined target audience over a set period of time.
-
D.
classic advertising campaign
A classic advertising campaign is a coordinated series of promotional messages, typically across multiple media channels, designed to build brand awareness and influence consumer behavior over a defined period.
-
E.
public campaign
A public campaign is a coordinated set of communication and outreach activities designed to inform, persuade, or mobilize a broad audience around a specific social, political, or commercial issue.
- F. None of above.
Provenance (1 batch)
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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:28 p.m.