Triple
T37360337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOC*NSF |
E927559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sports umbrella organization |
C42770
|
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: Sports umbrella organization Context triple: [NOC*NSF, instanceOf, Sports umbrella organization]
-
A.
Sports federation umbrella organization
chosen
A sports federation umbrella organization is a governing body that coordinates, supports, and represents multiple sports federations or associations under a unified structure and policy framework.
-
B.
sports organization collective
A sports organization collective is a coordinated group of sports entities—such as teams, clubs, leagues, or associations—that collaborate under shared governance, resources, or objectives to promote, manage, and develop athletic activities.
-
C.
sports tourism organization
A sports tourism organization is an entity that plans, promotes, and manages travel experiences centered around sporting events, activities, and destinations to attract visitors and stimulate local economic development.
-
D.
continental sports governing body
A continental sports governing body is an organization that oversees, regulates, and promotes specific sports or groups of sports across countries within a particular continent.
-
E.
segregated sports organization
A segregated sports organization is an athletic governing body or club that separates participants, teams, or competitions along lines such as race, gender, or other social categories, enforcing or perpetuating unequal access and opportunities in sport.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.