Triple
T8065862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerala Blasters FC |
E188241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian Super League club |
C23493
|
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: Indian Super League club Context triple: [Kerala Blasters FC, instanceOf, Indian Super League club]
-
A.
Canadian Premier League club
A Canadian Premier League club is a professional soccer team based in Canada that competes in the Canadian Premier League, representing its city or region in the country’s top domestic league.
-
B.
Major League Soccer club
A Major League Soccer club is a professional soccer team that competes in the top-tier men’s soccer league in the United States and Canada, operating under league-wide ownership and roster regulations.
-
C.
Returned and Services League club
A Returned and Services League club is a community-based organization that provides social, welfare, and commemorative support to current and former military personnel and their families, often operating venues for gatherings, events, and remembrance activities.
-
D.
Pakistan Super League franchise
A Pakistan Super League franchise is a professional Twenty20 cricket team that represents a specific city or region in the Pakistan Super League, operating as a commercial sports entity with its own players, management, branding, and fan base.
-
E.
Bangladesh Premier League team
A Bangladesh Premier League team is a professional Twenty20 cricket franchise that represents a specific city or region in Bangladesh’s top domestic T20 league, competing in seasonal tournaments organized by the Bangladesh Cricket Board.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:26 p.m.