Triple
T1327691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLB Collective Bargaining Agreement |
E28367
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collective bargaining agreement |
C3153
|
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: collective bargaining agreement Context triple: [MLB Collective Bargaining Agreement, instanceOf, collective bargaining agreement]
-
A.
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.
-
B.
labor union
A labor union is an organized association of workers formed to collectively negotiate with employers over wages, benefits, working conditions, and workplace rights.
-
C.
legal agreement
chosen
A legal agreement is a formally recognized arrangement between two or more parties that creates enforceable rights and obligations under the law.
-
D.
political agreement
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
-
E.
headquarters agreement
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.