Triple
T3071106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLB All-Star Week |
E64023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Major League Baseball property |
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 property Context triple: [MLB All-Star Week, instanceOf, Major League Baseball property]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Major League Baseball event
A Major League Baseball event represents a scheduled professional baseball game or related official activity organized under MLB, encompassing its participating teams, venue, timing, and associated outcomes.
-
E.
Major League Baseball rivalry
A Major League Baseball rivalry is a recurring, highly competitive relationship between two MLB teams characterized by historical significance, intense fan interest, and emotionally charged matchups that often influence seasons and legacies.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:02 p.m.