Triple
T25667320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Coast 2018 closing ceremony |
E643555
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-sport event closing ceremony |
C12338
|
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: multi-sport event closing ceremony Context triple: [Gold Coast 2018 closing ceremony, instanceOf, multi-sport event closing ceremony]
-
A.
sports closing ceremony
chosen
A sports closing ceremony is a celebratory event held at the end of a sports competition or tournament that features formal speeches, cultural performances, athlete recognition, and symbolic rituals to mark the conclusion of the games.
-
B.
paralympic closing ceremony
A Paralympic closing ceremony is the celebratory event that marks the end of the Paralympic Games, featuring cultural performances, athlete recognition, and the official handover to the next host city.
-
C.
multi-sport event
A multi-sport event is a large-scale organized competition in which athletes from various regions or groups compete across multiple different sports within a unified program and schedule.
-
D.
sports opening ceremony
A sports opening ceremony is a planned, often spectacular event that marks the official start of a sporting competition or tournament through performances, rituals, and formal presentations.
-
E.
participation in multi-sport event
Participation in multi-sport event represents an individual's or team's involvement in a competitive gathering that features multiple different sports or disciplines under a unified organizational framework.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 7:07 p.m.