Triple
T28177171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec Stadium (planning name) |
E715924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stadium planning name |
C6808
|
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: stadium planning name Context triple: [Aztec Stadium (planning name), instanceOf, stadium planning name]
-
A.
stadium design
Stadium design is the conceptual planning and architectural development of sports and event venues that optimize sightlines, crowd flow, safety, acoustics, and fan experience within structural and environmental constraints.
-
B.
football stadium moniker
chosen
A football stadium moniker is a distinctive, often informal or branded name used to identify and characterize a specific football venue.
-
C.
sports facilities planning project
A sports facilities planning project is a coordinated effort to assess needs, design, and strategically develop or upgrade sports venues and related infrastructure to optimally serve users and communities.
-
D.
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.
-
E.
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.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:17 p.m.