Triple
T1440622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivy League men's basketball |
E31061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college basketball conference competition |
C706
|
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: college basketball conference competition Context triple: [Ivy League men's basketball, instanceOf, college basketball conference competition]
-
A.
college basketball tournament
chosen
A college basketball tournament is a structured, multi-game competition in which collegiate teams compete in a bracketed or round-robin format to determine a champion.
-
B.
collegiate athletic conference
A collegiate athletic conference is an organized group of colleges and universities that compete against each other in intercollegiate sports under shared rules, governance, and scheduling agreements.
-
C.
NCAA Division I basketball team
An NCAA Division I basketball team is a collegiate basketball program that competes at the highest level of National Collegiate Athletic Association competition, adhering to specific scholarship, eligibility, and scheduling requirements.
-
D.
NCAA basketball tournament region
An NCAA basketball tournament region is a geographic and competitive subdivision of the tournament bracket that groups a set of teams who compete to produce one regional champion advancing to the Final Four.
-
E.
NCAA Division I men’s basketball team
An NCAA Division I men’s basketball team is a collegiate squad representing a university or college at the highest level of men’s basketball competition sanctioned by the National Collegiate Athletic Association.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 8 p.m.