Triple
T1182760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball Rules Committee |
E25175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational unit of Major League Baseball |
C7308
|
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: organizational unit of Major League Baseball Context triple: [Major League Baseball Rules Committee, instanceOf, organizational unit of Major League Baseball]
-
A.
Major League Baseball team
A Major League Baseball team is a professional sports organization that competes at the highest level of baseball in North America, consisting of players, coaches, and staff representing a specific city or region in the MLB.
-
B.
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.
-
C.
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.
-
D.
professional baseball team
A professional baseball team is an organized group of elite baseball players, coaches, and staff that competes in officially sanctioned leagues and tournaments under a shared identity, brand, and management structure.
-
E.
Major League Baseball stadium
A Major League Baseball stadium is a large, purpose-built sports venue designed to host professional baseball games, featuring a regulation field, spectator seating, player facilities, and amenities for fans.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.