Triple
T35301183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFL Competitions Department |
E1019508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports administration department |
C33905
|
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 administration department Context triple: [RFL Competitions Department, instanceOf, sports administration department]
-
A.
sports administration organization
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.
-
B.
sports department
chosen
A sports department is an organizational unit responsible for planning, managing, and promoting athletic programs, teams, events, and related resources within an institution or company.
-
C.
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.
-
D.
sports administration workforce
The sports administration workforce comprises professionals who plan, manage, and coordinate the business, operational, and governance aspects of sports organizations, events, and programs.
-
E.
sports architecture division
The sports architecture division is a specialized unit focused on planning, designing, and overseeing the construction or renovation of sports facilities and venues to optimize performance, safety, and spectator experience.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.