Triple
T7597126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varsity Match at Twickenham Stadium |
E179884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university sports rivalry |
C778
|
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: university sports rivalry Context triple: [Varsity Match at Twickenham Stadium, instanceOf, university sports rivalry]
-
A.
sports rivalry
chosen
A sports rivalry is a competitive relationship between teams, athletes, or fan bases characterized by repeated contests, heightened emotions, and historical or cultural significance that intensifies their matchups.
-
B.
college basketball rivalry
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.
-
C.
NCAA sport
An NCAA sport is an organized athletic activity governed by the National Collegiate Athletic Association in which college teams compete under standardized rules and eligibility requirements.
-
D.
collegiate athletes
Collegiate athletes are students enrolled in higher education institutions who participate in organized, competitive sports sanctioned by collegiate athletic associations while balancing academic and athletic commitments.
-
E.
university football team
A university football team is an organized group of student-athletes representing their institution in competitive American football, typically governed by collegiate athletic associations and supported by the campus community.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:53 p.m.