Triple
T27796199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakota Wizards (franchise lineage) |
E702116
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional basketball franchise |
C388
|
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 basketball franchise Context triple: [Dakota Wizards (franchise lineage), instanceOf, professional basketball franchise]
-
A.
professional basketball team
chosen
A professional basketball team is an organized group of elite basketball players, coaches, and support staff that competes in officially sanctioned leagues and tournaments as a single franchise or club.
-
B.
professional basketball league
A professional basketball league is an organized competition in which franchised or club teams of paid, elite basketball players play a structured season of games culminating in playoffs and a championship.
-
C.
NBA team
An NBA team is a professional basketball organization that competes in the National Basketball Association, consisting of players, coaches, and staff representing a specific city or region.
-
D.
professional basketball team season
A professional basketball team season is the organized period during which a team competes in a league’s scheduled games, tournaments, and playoffs, encompassing player performance, team strategy, transactions, and overall results.
-
E.
professional basketball game
A professional basketball game is a competitive sporting event in which organized teams of elite players follow official basketball rules to score points by shooting a ball through the opponent’s hoop within a set time.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:31 p.m.