Triple
T1331882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 MLB strike |
E28660
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Major League Baseball strike |
C6466
|
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 strike Context triple: [1981 MLB strike, instanceOf, Major League Baseball 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 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.
-
C.
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.
-
D.
baseball scandal
A baseball scandal is a widely publicized incident in which players, teams, or officials violate rules or ethical standards—such as through cheating, gambling, or performance-enhancing drugs—thereby undermining the integrity of the sport.
-
E.
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.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.