Triple
T37919741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Bulldogs swimming and diving |
E945921
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collegiate swimming and diving team |
C50231
|
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 swimming and diving team Context triple: [Georgia Bulldogs swimming and diving, instanceOf, collegiate swimming and diving 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.
swimming and diving team
chosen
A swimming and diving team is an organized group of athletes who train and compete together in aquatic events that involve racing in the water and performing judged dives.
-
C.
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.
-
D.
swimming and diving league
A swimming and diving league is an organized association that coordinates competitive swim and dive events, schedules, rules, and rankings among participating teams or clubs.
-
E.
women’s collegiate swimming and diving competition
A women’s collegiate swimming and diving competition is an organized meet where female student-athletes representing colleges or universities compete in various swimming strokes and diving events under standardized rules and scoring.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.