Triple
T10120339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonwealth Games men's doubles |
E223270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Commonwealth Games badminton discipline |
C27453
|
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: Commonwealth Games badminton discipline Context triple: [Commonwealth Games men's doubles, instanceOf, Commonwealth Games badminton discipline]
-
A.
Commonwealth Games
The Commonwealth Games is an international multi-sport event held every four years, featuring athletes from nations and territories of the Commonwealth of Nations competing in a wide range of sports and disciplines.
-
B.
British Empire and Commonwealth Games edition
A British Empire and Commonwealth Games edition represents a specific occurrence of the multi-sport event, detailing its host city, year, participating nations, sports contested, and overall organizational context within the broader history of the Games.
-
C.
Malaysian badminton player
A Malaysian badminton player is an athlete from Malaysia who competes in the sport of badminton at national and/or international levels, representing clubs, states, or the country in various tournaments.
-
D.
Commonwealth-associated event
A Commonwealth-associated event is any organized occurrence, ceremony, or activity that is formally linked to, sponsored by, or held in recognition of the Commonwealth of Nations or its member states.
-
E.
Highland games
Highland games are traditional Scottish athletic and cultural festivals featuring strength competitions, music, dance, and clan heritage celebrations.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:04 p.m.