Triple
T13960655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Volleyball Federation |
E335782
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | volleyball governing body |
C34426
|
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: volleyball governing body Context triple: [International Volleyball Federation, instanceOf, volleyball governing body]
-
A.
professional volleyball club
A professional volleyball club is an organized sports entity that recruits and trains elite volleyball players to compete in official leagues and tournaments under a unified brand and management structure.
-
B.
volleyball player
A volleyball player is an athlete who participates in the sport of volleyball, using specialized skills like serving, passing, setting, attacking, blocking, and digging to compete as part of a team on an indoor court or beach.
-
C.
basketball federation
A basketball federation is an organized governing body responsible for overseeing, regulating, and promoting basketball activities, competitions, and development within a specific region or country.
-
D.
international volleyball tournament
An international volleyball tournament is a large-scale, organized competition in which national or club teams from multiple countries play a series of matches to determine a champion under standardized rules and schedules.
-
E.
Eurasian sports organization
A Eurasian sports organization is an entity that governs, promotes, and coordinates athletic activities, competitions, and development programs across countries spanning Europe and Asia.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.