Triple
T31454517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badminton World Federation |
E802413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | badminton governing body |
C49115
|
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: badminton governing body Context triple: [Badminton World Federation, instanceOf, badminton governing body]
-
A.
badminton association
chosen
A badminton association is an organized group or governing body that promotes, regulates, and supports badminton activities, events, and players within a specific region or community.
-
B.
badminton club
A badminton club is an organized group or community where individuals regularly gather to play, practice, and sometimes compete in badminton, often providing access to courts, equipment, coaching, and social events.
-
C.
national governing body for tennis
A national governing body for tennis is an organization responsible for overseeing, regulating, and promoting the sport of tennis within a specific country, including organizing competitions, setting standards, and representing the nation in international tennis affairs.
-
D.
table tennis association
A table tennis association is an organized group that promotes, regulates, and supports table tennis activities, competitions, and player development within a specific region or community.
-
E.
international badminton tournament
An international badminton tournament is a large-scale, officially sanctioned competition where elite players or national teams from multiple countries compete in structured matches to determine champions across various event categories.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:15 p.m.