Triple
T6453285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodge City A's |
E139926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | summer collegiate baseball team |
C11587
|
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: summer collegiate baseball team Context triple: [Dodge City A's, instanceOf, summer collegiate baseball team]
-
A.
collegiate summer baseball team
chosen
A collegiate summer baseball team is a temporary, amateur squad composed primarily of college players who compete in organized leagues during the summer to develop skills, gain exposure, and maintain NCAA eligibility.
-
B.
university baseball team
A university baseball team is an organized group of student-athletes representing their institution in collegiate baseball competitions, practices, and related activities.
-
C.
NCAA Division I baseball tournament
The NCAA Division I baseball tournament is an annual postseason championship event in U.S. college baseball where selected Division I teams compete in a multi-round, elimination-style format culminating in the College World Series to determine the national champion.
-
D.
college baseball division
A college baseball division is an organizational grouping of collegiate baseball teams, typically based on competitive level, institutional size, and governing body rules, that structures regular-season play and championship qualification.
-
E.
college baseball rivalry game
A college baseball rivalry game is a highly anticipated, emotionally charged matchup between two collegiate teams with a long-standing competitive history, often drawing large crowds and heightened media attention.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:47 p.m.