Triple
T22246260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball All-Star Game |
E549850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | annual baseball exhibition game |
C2446
|
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: annual baseball exhibition game Context triple: [Major League Baseball All-Star Game, instanceOf, annual baseball exhibition game]
-
A.
annual sporting event
An annual sporting event is a recurring, organized athletic competition held once each year, typically featuring established rules, participants, and traditions that attract spectators and media attention.
-
B.
Major League Baseball season
A Major League Baseball season is the annual, structured schedule of professional baseball games, including preseason, regular season, and postseason play, in which MLB teams compete to determine league and World Series champions.
-
C.
Major League Baseball championship series
A Major League Baseball championship series is a postseason best-of-seven playoff between league champions (or top qualifiers) that determines the overall MLB champion for a given season.
-
D.
Major League Baseball event
A Major League Baseball event represents a scheduled professional baseball game or related official activity organized under MLB, encompassing its participating teams, venue, timing, and associated outcomes.
-
E.
baseball all-star game
chosen
A baseball all-star game is a special exhibition match that features the top players from a league, typically selected by fans, coaches, and media, to showcase their skills in a celebratory mid-season event.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:38 p.m.