Triple
T24026734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball expansion in the 1990s |
E594984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Major League Baseball expansion |
C6344
|
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 expansion Context triple: [Major League Baseball expansion in the 1990s, instanceOf, Major League Baseball expansion]
-
A.
Major League Baseball entity
chosen
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.
-
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 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.
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.
-
E.
Major League Baseball television package
A Major League Baseball television package is a bundled set of broadcast rights that allows a network or service to televise a defined slate of MLB games over a specified period and territory.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:54 p.m.