Triple
T16051511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing 2022 legacy plan |
E389362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Olympic legacy plan |
C36896
|
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 legacy plan Context triple: [Beijing 2022 legacy plan, instanceOf, Olympic legacy plan]
-
A.
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.
-
B.
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.
-
C.
Olympic theme
A grand, inspiring atmosphere that celebrates international unity, athletic excellence, and the ceremonial traditions of the Olympic Games.
-
D.
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.
-
E.
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.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:56 a.m.