Triple
T8189140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stewards of Henley Royal Regatta |
E191260
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports event organizing body |
C5629
|
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 event organizing body Context triple: [Stewards of Henley Royal Regatta, instanceOf, sports event organizing body]
-
A.
sports governing committee
A sports governing committee is an organized body responsible for setting rules, overseeing competitions, and making policy decisions to regulate and promote a particular sport or group of sports.
-
B.
sports administration organization
chosen
A sports administration organization is an entity responsible for governing, regulating, and managing the operations, policies, and development of sports activities, leagues, or associations within its jurisdiction.
-
C.
sports officiating organization
A sports officiating organization is an entity that recruits, trains, assigns, and oversees referees and officials to ensure fair and consistent enforcement of rules in athletic competitions.
-
D.
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.
-
E.
Olympic Games organizer
An Olympic Games organizer is responsible for planning, coordinating, and managing all aspects of hosting the Olympic Games, including logistics, venues, athletes, security, ceremonies, and compliance with International Olympic Committee regulations.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:41 p.m.