Triple
T5963976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Wildcats cross country program |
E132707
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collegiate cross country team |
C5504
|
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 cross country team Context triple: [Arizona Wildcats cross country program, instanceOf, collegiate cross country team]
-
A.
NCAA Division I cross country team
chosen
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.
-
B.
NCAA Division I cross country league
An NCAA Division I cross country league is an organized group of Division I colleges and universities that compete against each other in regular-season and championship cross country meets under NCAA rules and standards.
-
C.
college women’s track and field team
A college women’s track and field team is a group of female student-athletes who train and compete in a variety of running, jumping, and throwing events for their institution.
-
D.
collegiate men’s rowing team
A collegiate men’s rowing team is an organized group of male student-athletes who train and compete in rowing events for their college or university, representing the institution in intercollegiate regattas.
-
E.
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.
- 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_69c0086c2364819091e9fe2f58fa2517 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:03 p.m.