Triple
T36129400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLB Little League Classic |
E1044973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Major League Baseball special event |
C1416
|
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: Major League Baseball special event Context triple: [MLB Little League Classic, instanceOf, Major League Baseball special event]
-
A.
Major League Baseball event
chosen
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.
-
B.
Major League Baseball divisional race
A Major League Baseball divisional race is the season-long competition among teams within the same division to finish with the best record and secure a playoff berth.
-
C.
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.
-
D.
Major League Baseball entity
A Major League Baseball entity represents any organization, team, venue, event, or official construct that participates in, governs, or is formally recognized within the structure of Major League Baseball.
-
E.
Major League Baseball television program
A Major League Baseball television program is a broadcast show that presents live or recorded MLB games, along with related commentary, analysis, highlights, and features for viewers.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.