Triple
T24237932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball labor disputes |
E603141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports labor conflict |
C6970
|
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: sports labor conflict Context triple: [Major League Baseball labor disputes, instanceOf, sports labor conflict]
-
A.
sports labor dispute
chosen
A sports labor dispute is a conflict between athletes (or their unions) and leagues, teams, or governing bodies over employment conditions such as salaries, benefits, free agency, and work rules, often resulting in strikes, lockouts, or other disruptions to competition.
-
B.
sports labor system
The sports labor system is the structured network of rules, institutions, and relationships that govern how athletes’ work is organized, compensated, controlled, and negotiated within professional and amateur sports.
-
C.
sports strike
A sports strike is a collective work stoppage by athletes, typically organized through their union, to protest labor conditions or negotiate better terms with leagues or team owners.
-
D.
Major League Baseball labor strike
A Major League Baseball labor strike is a work stoppage initiated by MLB players, through their union, to protest or negotiate changes to employment conditions such as salaries, benefits, free agency, or working rules with team owners.
-
E.
sports occupation
A sports occupation is a professional role in which an individual participates in, supports, or manages athletic activities, events, or organizations as a primary source of employment.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:03 a.m.