Triple
T1357684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994–95 MLB strike |
E29025
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Major League Baseball labor strike |
C6969
|
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 labor strike Context triple: [1994–95 MLB strike, instanceOf, Major League Baseball labor strike]
-
A.
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.
-
B.
Major League Baseball rivalry
A Major League Baseball rivalry is a recurring, highly competitive relationship between two MLB teams characterized by historical significance, intense fan interest, and emotionally charged matchups that often influence seasons and legacies.
-
C.
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.
-
D.
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.
-
E.
baseball agreement
A baseball agreement is a formal contract outlining the terms, conditions, and obligations between parties involved in professional or amateur baseball activities, such as players, teams, leagues, or sponsors.
- F. None of above. chosen
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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:56 p.m.