Triple
T707526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nationals Park |
E14133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Major League Baseball ballpark |
C935
|
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 ballpark Context triple: [Nationals Park, instanceOf, Major League Baseball ballpark]
-
A.
Major League Baseball stadium
chosen
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.
-
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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:36 p.m.