Triple
T634969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT&T Stadium |
E16603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | domed stadium |
C344
|
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: domed stadium Context triple: [AT&T Stadium, instanceOf, domed stadium]
-
A.
multi-purpose stadium
A multi-purpose stadium is a large, versatile venue designed to host a variety of events, such as sports games, concerts, and community gatherings, by accommodating different configurations and audiences.
-
B.
sports venue
chosen
A sports venue is a designated facility or location equipped to host organized athletic events, competitions, and related spectator activities.
-
C.
sports venue feature
A sports venue feature is a distinct physical or functional element within a sports facility—such as seating areas, scoreboards, playing surfaces, or lighting systems—that supports or enhances the hosting and viewing of sporting events.
-
D.
stadium authority
A stadium authority is an organization, typically public or quasi-public, responsible for owning, managing, financing, and overseeing the operation and development of a sports or entertainment stadium and its surrounding facilities.
-
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.
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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.