Triple
T4543835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1967–68 ABA season |
E109999
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Basketball Association season |
C1281
|
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: American Basketball Association season Context triple: [1967–68 ABA season, instanceOf, American Basketball Association season]
-
A.
basketball league season
chosen
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.
-
B.
National Basketball Association division
A National Basketball Association division is a grouping of NBA teams, typically organized by geographic region, used to structure the regular-season schedule and standings within the league’s conferences.
-
C.
NBA conference
An NBA conference is a major organizational division of the National Basketball Association, grouping teams primarily by geography (Eastern or Western) for the purposes of scheduling, standings, and playoff structure.
-
D.
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.
-
E.
National Basketball Association event
A National Basketball Association event is an organized, league-sanctioned occurrence—such as a game, draft, or ceremony—where NBA teams, players, officials, and stakeholders participate under official NBA rules and branding.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.