Triple
T14105818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Olympic Partner programme |
E339501
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Olympic sponsorship programme |
C33451
|
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 sponsorship programme Context triple: [The Olympic Partner programme, instanceOf, Olympic sponsorship programme]
-
A.
Olympic Games promotional campaign
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 legacy organization
An Olympic legacy organization is an entity dedicated to preserving, managing, and enhancing the long-term social, economic, and environmental benefits of hosting the Olympic Games for the host city, region, and nation.
-
D.
Olympic Games design element
An Olympic Games design element is a visual or structural component—such as logos, pictograms, color schemes, or venue aesthetics—created to embody and communicate the identity, values, and spirit of a specific Olympic Games.
-
E.
Olympic symbol
The Olympic symbol is a design of five interlocking rings in blue, yellow, black, green, and red on a white background, representing the union of the five inhabited continents and the meeting of athletes from around the world at the Olympic Games.
- F. None of above. chosen
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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:22 p.m.