Triple
T23954935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Division |
E603759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Minor League Baseball division |
C7780
|
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: Minor League Baseball division Context triple: [Northern Division, instanceOf, Minor League Baseball division]
-
A.
minor league baseball division
chosen
A minor league baseball division is an organizational grouping of teams at a specific competitive level within professional baseball’s developmental system, structured to facilitate regional play, player development, and progression toward the major leagues.
-
B.
minor league
A minor league is a lower-tier professional sports organization where athletes develop their skills and gain experience before potentially advancing to a major league.
-
C.
Major League Baseball division
A Major League Baseball division is a grouping of teams within either the American or National League, organized primarily by geography, that compete against each other throughout the regular season to determine playoff qualification.
-
D.
Minor League Baseball team name
A Minor League Baseball team name is a distinctive, often regionally inspired title that identifies and brands a professional baseball club affiliated with Major League Baseball’s developmental system.
-
E.
minor league baseball player
A minor league baseball player is an athlete who plays professional baseball on a team affiliated with a Major League organization, developing skills and competing at lower-tier levels with the goal of reaching the major leagues.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:21 p.m.