Triple
T32338848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Big 5 schools |
E826251
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college basketball rivalry group |
C21136
|
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 rivalry group Context triple: [Philadelphia Big 5 schools, instanceOf, college basketball rivalry group]
-
A.
college basketball rivalry
chosen
A college basketball rivalry is a recurring, highly competitive series of games between two collegiate teams characterized by historical significance, regional or conference proximity, and intense fan and media interest.
-
B.
college basketball conference tournament titles
College basketball conference tournament titles represent the championships awarded to teams that win their respective conference’s postseason tournament, often determining automatic qualification for the NCAA Tournament.
-
C.
NCAA rivalry
An NCAA rivalry is a recurring, highly competitive athletic contest between two college or university programs, often fueled by historical, geographic, or cultural tensions and traditions.
-
D.
college basketball tournament
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.
-
E.
college basketball season
A college basketball season is the annual cycle of organized practices, regular-season games, conference tournaments, and postseason play in which collegiate teams compete to determine rankings, championships, and player development outcomes.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:48 a.m.