Triple
T10402912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehigh–Cornell wrestling rivalry |
E245190
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college wrestling 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: college wrestling rivalry Context triple: [Lehigh–Cornell wrestling rivalry, instanceOf, college wrestling rivalry]
-
A.
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.
-
B.
NCAA Division I wrestling team
An NCAA Division I wrestling team is a collegiate athletic program that competes at the highest level of U.S. college wrestling, fielding student-athletes in various weight classes under NCAA Division I rules and regulations.
-
C.
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.
-
D.
university sports competitions
University sports competitions are organized athletic events in which teams or individuals representing higher education institutions compete under standardized rules to promote physical excellence, school spirit, and intercollegiate rivalry.
-
E.
college fencing tournament
A college fencing tournament is a competitive event where collegiate fencing teams and individual student-athletes compete in organized bouts across different weapon categories to determine rankings and champions.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:08 p.m.