Triple
T3410768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Counter Logic Gaming |
E71887
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional gaming team organization |
C3783
|
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: professional gaming team organization Context triple: [Counter Logic Gaming, instanceOf, professional gaming team organization]
-
A.
esports team
chosen
An esports team is an organized group of players who competitively participate in video game tournaments and leagues under a shared name, brand, and management structure.
-
B.
professional golf team
A professional golf team is an organized group of elite golfers, coaches, and support staff who compete collaboratively in tournaments and leagues under a shared identity, brand, and management structure.
-
C.
video game organization
A video game organization is a structured entity that manages the development, publishing, promotion, or competitive play of video games through coordinated teams, resources, and strategic planning.
-
D.
professional indoor football team
A professional indoor football team is an organized sports franchise that competes in structured indoor football leagues, featuring paid athletes playing modified American football under a roofed arena with specialized rules and field dimensions.
-
E.
semi-professional sports team
A semi-professional sports team is an organized group of athletes who compete in structured leagues or competitions while receiving limited financial compensation, often balancing their athletic commitments with other employment or responsibilities.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:15 p.m.