Triple
T27920270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA rebounding title |
E706186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NBA statistical championship |
C12306
|
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: NBA statistical championship Context triple: [NBA rebounding title, instanceOf, NBA statistical championship]
-
A.
basketball statistical honor
chosen
A basketball statistical honor is a formal recognition awarded to a player for achieving exceptional performance in specific statistical categories over a defined period, such as a game, season, or career.
-
B.
NBA championship
An NBA championship is the annual title awarded to the team that wins the National Basketball Association’s postseason playoffs, culminating in victory in the NBA Finals series.
-
C.
era in National Basketball Association history
An era in National Basketball Association history is a distinct time period characterized by particular styles of play, dominant teams and players, league rules, and cultural or commercial developments that collectively define the league’s identity during that span.
-
D.
basketball statistics database
A basketball statistics database is a structured repository that stores, organizes, and provides access to detailed data about games, teams, players, and performance metrics over time.
-
E.
National Basketball Association honor
A National Basketball Association honor is a formal recognition awarded by the NBA to players, coaches, teams, or contributors for outstanding performance, achievement, or service within the 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:56 p.m.