Triple
T17453398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunil Gulati |
E424970
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | soccer administrator |
C31968
|
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: soccer administrator Context triple: [Sunil Gulati, instanceOf, soccer administrator]
-
A.
soccer league operator
A soccer league operator is an entity responsible for organizing, managing, and regulating soccer competitions, including scheduling matches, enforcing rules, coordinating teams and officials, and overseeing league logistics and governance.
-
B.
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.
-
C.
association football manager
An association football manager is the individual responsible for leading a football team by planning tactics, selecting players, overseeing training, and making strategic decisions before and during matches.
-
D.
sports commissioner
chosen
A sports commissioner is the chief executive and governing authority of a professional sports league, responsible for overseeing operations, enforcing rules, negotiating major agreements, and safeguarding the integrity and commercial success of the league.
-
E.
rugby union administrator
A rugby union administrator is a professional responsible for organizing, managing, and overseeing the operations, governance, and development of rugby union activities within a club, region, or governing body.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.