Triple
T2090770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisville Colonels |
E32663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defunct Major League Baseball team |
C385
|
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: defunct Major League Baseball team Context triple: [Louisville Colonels, instanceOf, defunct Major League Baseball team]
-
A.
Major League Baseball entity
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.
-
B.
Major League Baseball team
chosen
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.
-
C.
organizational unit of Major League Baseball
An organizational unit of Major League Baseball is a formal structural division—such as a league, division, team, or affiliated entity—established to manage competition, governance, and operations within the MLB system.
-
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 strike
A Major League Baseball strike is a work stoppage in which MLB players collectively refuse to play games, typically to gain leverage in labor negotiations with team owners over issues like salaries, benefits, and working conditions.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:43 p.m.