Triple
T6568426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball Labor Policy Committee |
E153971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Major League Baseball committee |
C6344
|
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 committee Context triple: [Major League Baseball Labor Policy Committee, instanceOf, Major League Baseball committee]
-
A.
baseball commissioner
A baseball commissioner is the chief executive and governing authority of a professional baseball league, responsible for overseeing league operations, enforcing rules, and safeguarding the integrity of the sport.
-
B.
Major League Baseball entity
chosen
A Major League Baseball entity represents any organization, team, venue, event, or official construct that participates in, governs, or is formally recognized within the structure of Major League Baseball.
-
C.
Commissioner of Major League Baseball
The Commissioner of Major League Baseball is the chief executive responsible for overseeing the operations, integrity, and best interests of professional baseball in North America.
-
D.
Major League Baseball division
A Major League Baseball division is a grouping of teams within either the American or National League, organized primarily by geography, that compete against each other throughout the regular season to determine playoff qualification.
-
E.
baseball league
A baseball league is an organized association of baseball teams that compete against each other according to a structured schedule and shared rules over a defined season.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 1:53 p.m.