Triple
T19738025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1972–73 Kentucky Colonels |
E474038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional basketball team season |
C42548
|
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 team season Context triple: [1972–73 Kentucky Colonels, instanceOf, professional basketball team season]
-
A.
professional basketball team
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.
basketball league season
A basketball league season is a structured period of competition in which participating teams play a scheduled series of games to determine standings, playoff qualifiers, and ultimately a champion.
-
C.
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.
-
D.
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.
-
E.
professional baseball league season
A professional baseball league season is the organized, time-bounded schedule of official games, standings, and related competitions in which member teams play to determine rankings, statistics, and champions for that year or period.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:47 p.m.