Triple
T23812848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Host City Contract |
E589906
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Olympic Games contract |
C48082
|
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 Games contract Context triple: [Host City Contract, instanceOf, Olympic Games contract]
-
A.
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.
-
B.
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.
-
C.
Olympic legacy plan
An Olympic legacy plan is a strategic framework designed to ensure that the long-term social, economic, environmental, and infrastructural benefits of hosting the Olympic Games are realized and sustained for the host city and nation.
-
D.
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.
-
E.
Formula One commercial agreement
A Formula One commercial agreement is a contractual framework that governs the distribution of revenues, commercial rights, and obligations among the sport’s stakeholders, including teams, the commercial rights holder, and governing bodies.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 7:57 p.m.