Triple
T14951136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division III men’s lacrosse |
E372795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | men’s lacrosse division |
C13411
|
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: men’s lacrosse division Context triple: [NCAA Division III men’s lacrosse, instanceOf, men’s lacrosse division]
-
A.
NCAA Division I men’s lacrosse program
An NCAA Division I men’s lacrosse program is a collegiate athletic team and its associated organizational structure that competes at the highest level of NCAA men’s lacrosse, encompassing student-athletes, coaches, facilities, and institutional support under NCAA Division I rules and standards.
-
B.
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.
-
C.
NCAA Division I men's lacrosse conference
chosen
An NCAA Division I men's lacrosse conference is an organized group of Division I colleges and universities that compete against each other in men's lacrosse under shared governance, scheduling, and championship structures.
-
D.
box lacrosse league
A box lacrosse league is an organized competition structure in which multiple indoor lacrosse teams regularly play scheduled games under a common set of rules and governance.
-
E.
indoor lacrosse league
An indoor lacrosse league is an organized competition structure where multiple teams regularly play lacrosse games in enclosed arenas under a standardized set of rules and schedules.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:39 a.m.