Triple

T31486293
Position Surface form Disambiguated ID Type / Status
Subject London 2012 Olympic legacy masterplan E803285 entity
Predicate instanceOf P0 FINISHED
Object post-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: post-Olympic legacy plan
Context triple: [London 2012 Olympic legacy masterplan, instanceOf, post-Olympic legacy plan]
  • A. Olympic legacy plan chosen
    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.
  • B. 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.
  • C. sports event legacy strategy
    A sports event legacy strategy is a long-term, planned approach to ensure that hosting a sporting event delivers enduring social, economic, environmental, and infrastructural benefits for the host community well beyond the event itself.
  • D. post-Olympic tour
    A post-Olympic tour is a series of exhibition events in which Olympic athletes travel to various locations after the Games to perform, compete in non-official showcases, and engage with fans and sponsors.
  • E. planned mega-event
    A planned mega-event is a large-scale, one-time or infrequent gathering, such as a major sporting, cultural, or political event, that is scheduled in advance and designed to attract substantial international attention, visitors, and investment.
  • 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_69f348ca04508190ba9379b5329dfd75 completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 9:35 p.m.