Triple
T1162275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon State Beavers men’s rowing |
E24519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collegiate men’s rowing team |
C7101
|
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: collegiate men’s rowing team Context triple: [Oregon State Beavers men’s rowing, instanceOf, collegiate men’s rowing team]
-
A.
college men’s swimming and diving team
A college men’s swimming and diving team is an organized group of male student-athletes who train and compete in collegiate-level swimming and diving events under institutional and athletic conference regulations.
-
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.
collegiate fencing team
A collegiate fencing team is a university-sponsored group of student-athletes who train and compete in organized foil, épée, and/or sabre events against other schools under collegiate athletic regulations.
-
D.
NCAA Division I cross country team
An NCAA Division I cross country team is a collegiate athletic squad composed of distance runners who train and compete in long-distance races at the highest level of intercollegiate competition in the United States.
-
E.
college women’s swimming and diving team
A college women’s swimming and diving team is an organized group of female student-athletes who train, compete, and represent their institution in intercollegiate swimming and diving events.
- F. None of above. chosen
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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.