Triple
T14996285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICON Venue Group |
E373965
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stadium development firm |
C28401
|
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 development firm Context triple: [ICON Venue Group, instanceOf, stadium development firm]
-
A.
sports venue development
chosen
Sports venue development is the planning, financing, design, and construction of facilities for sporting events, integrating stakeholder needs, regulatory requirements, and long-term community and commercial objectives.
-
B.
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.
-
C.
infrastructure developer
An infrastructure developer designs, builds, and maintains the underlying systems, tools, and automation that support reliable, scalable, and secure software deployment and operations.
-
D.
station redevelopment organization
A station redevelopment organization is an entity responsible for planning, coordinating, and executing the modernization and transformation of railway or transit stations to improve functionality, accessibility, and surrounding urban environments.
-
E.
stadium modernization project
A stadium modernization project is a coordinated initiative to upgrade an existing sports venue’s infrastructure, technology, amenities, and safety features to meet contemporary standards and enhance the overall spectator and event experience.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:53 a.m.