Triple
T26411101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan Rules |
E663961
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | basketball defensive strategy |
C48561
|
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: basketball defensive strategy Context triple: [Jordan Rules, instanceOf, basketball defensive strategy]
-
A.
defensive basketball system
chosen
A defensive basketball system is a coordinated set of strategies, formations, and responsibilities designed to prevent the opposing team from scoring by disrupting their offensive plays.
-
B.
basketball offensive system
A basketball offensive system is a structured set of principles, plays, and spacing rules designed to coordinate player movement and decision-making to create high-quality scoring opportunities.
-
C.
basketball discipline
Basketball discipline is the consistent application of focus, effort, and self-control in training, gameplay, and behavior to improve performance and uphold the standards of the sport.
-
D.
defensive play
Defensive play is a strategic approach in games or sports focused on preventing the opponent from scoring or gaining advantage, often by prioritizing protection, positioning, and risk minimization over aggressive advancement.
-
E.
basketball play
A basketball play is a coordinated, pre-planned sequence of player movements and actions designed to create a strategic advantage on offense or defense during a game.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:38 p.m.