Triple
T11298476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke men's basketball |
E267514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Atlantic Coast Conference men's basketball team |
C2211
|
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: Atlantic Coast Conference men's basketball team Context triple: [Duke men's basketball, instanceOf, Atlantic Coast Conference men's basketball team]
-
A.
men's basketball team
A men's basketball team is an organized group of male players who train and compete together in the sport of basketball under a shared identity, strategy, and coaching structure.
-
B.
NCAA Division I men’s basketball team
chosen
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.
-
C.
university basketball team
A university basketball team is an organized group of student-athletes representing their institution in competitive collegiate basketball, balancing academic responsibilities with training, teamwork, and intercollegiate games.
-
D.
university basketball team
A university basketball team is an organized group of student-athletes representing their institution in competitive intercollegiate basketball games and tournaments.
-
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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.