Triple
T31914911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland–Johns Hopkins lacrosse rivalry |
E814800
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college lacrosse rivalry |
C46781
|
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 lacrosse rivalry Context triple: [Maryland–Johns Hopkins lacrosse rivalry, instanceOf, college lacrosse rivalry]
-
A.
college men’s lacrosse team
A college men’s lacrosse team is an organized group of male student-athletes representing a college or university in intercollegiate lacrosse competition, combining athletic performance with academic commitments.
-
B.
college women's lacrosse conference competition
A college women's lacrosse conference competition is an organized series of games in which women's lacrosse teams from member colleges within the same athletic conference compete to determine conference standings and championships.
-
C.
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.
-
D.
NCAA rivalry
chosen
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.
-
E.
field lacrosse competition
A field lacrosse competition is an organized sporting event in which teams play regulation field lacrosse matches under standardized rules to determine a winner or ranking.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:02 a.m.