Triple
T16531484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County Championship clubs |
E401576
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cricket team collective |
C29230
|
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: cricket team collective Context triple: [County Championship clubs, instanceOf, cricket team collective]
-
A.
domestic cricket team
chosen
A domestic cricket team is an organized group of players representing a specific region, state, province, or club within a country in officially sanctioned domestic cricket competitions.
-
B.
Indian domestic cricket team
An Indian domestic cricket team is a regional or institutional side that competes in national tournaments like the Ranji Trophy, Vijay Hazare Trophy, and Syed Mushtaq Ali Trophy, serving as a key platform for player development and selection to higher levels of Indian cricket.
-
C.
national cricket team
A national cricket team is an officially selected group of players who represent their country in international cricket competitions and matches.
-
D.
cricket franchise
A cricket franchise is a commercially operated, brand-based cricket team or organization that participates in professional leagues under a specific ownership, identity, and revenue model.
-
E.
Bangladeshi domestic cricket team
A Bangladeshi domestic cricket team is a professional or semi-professional cricket side that represents a regional division, club, or franchise within Bangladesh’s internal cricket structure, competing in national tournaments such as the National Cricket League, Dhaka Premier Division, and Bangladesh Premier League.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:15 a.m.