Triple
T31674028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney 2000 Olympic ceremonies |
E808348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | opening and closing ceremonies |
C60186
|
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: opening and closing ceremonies Context triple: [Sydney 2000 Olympic ceremonies, instanceOf, opening and closing ceremonies]
-
A.
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.
-
B.
sports closing ceremony
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.
-
C.
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.
-
D.
segment of Olympic Games opening ceremony
A segment of the Olympic Games opening ceremony is a distinct, thematically unified portion of the event’s program that combines performances, protocols, and visual elements to contribute to the overall narrative and symbolism of the ceremony.
-
E.
athletic festival
An athletic festival is a planned event featuring a variety of sports competitions, physical activities, and related celebrations that bring participants and spectators together in a communal setting.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:02 p.m.