Triple
T28700730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary 1988 Olympic publicity campaigns |
E729542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Olympic publicity campaign |
C25892
|
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: Olympic publicity campaign Context triple: [Calgary 1988 Olympic publicity campaigns, instanceOf, Olympic publicity campaign]
-
A.
Olympic Games promotional campaign
chosen
An Olympic Games promotional campaign is a coordinated set of marketing and communication activities designed to build global awareness, excitement, and engagement around the upcoming Olympic Games, its host city, athletes, and values.
-
B.
Olympic Games slogan
A concise, memorable phrase used to encapsulate and promote the core values, spirit, and identity of a specific edition of the Olympic Games.
-
C.
Olympic sponsorship programme
An Olympic sponsorship programme is a structured initiative through which companies provide financial or in-kind support to the Olympic Games in exchange for exclusive marketing rights, brand association, and global promotional opportunities.
-
D.
Olympic education initiative
An Olympic education initiative is a structured program that uses the values, history, and practices of the Olympic Movement to promote physical education, intercultural understanding, fair play, and personal development among learners.
-
E.
Olympic Games poster
An Olympic Games poster is a visually striking promotional graphic that represents a specific edition of the Olympic Games, conveying its host city, year, and spirit through symbolic imagery and design.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:42 a.m.