Triple
T6568425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball Labor Policy Committee |
E153971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | labor relations committee |
C21600
|
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: labor relations committee Context triple: [Major League Baseball Labor Policy Committee, instanceOf, labor relations committee]
-
A.
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.
-
B.
labor–management partnership
A labor–management partnership is a collaborative relationship between employees (often through unions) and employers designed to jointly address workplace issues, improve organizational performance, and enhance job quality through shared decision-making and problem-solving.
-
C.
labor commissioner
A labor commissioner is a public official responsible for enforcing labor laws, protecting workers’ rights, and overseeing workplace standards and employment practices within a jurisdiction.
-
D.
labor department
The labor department is a governmental or organizational unit responsible for overseeing employment standards, workplace safety, labor relations, and workforce development policies and programs.
-
E.
labor movement organization
A labor movement organization is a collective entity that coordinates, represents, and advocates for workers’ interests in improving wages, working conditions, and labor rights through negotiation, mobilization, and political action.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 1:53 p.m.