Triple
T22853233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn Athletics facilities |
E566407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | athletic facilities system |
C242
|
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: athletic facilities system Context triple: [Penn Athletics facilities, instanceOf, athletic facilities system]
-
A.
sports and recreation facility
chosen
A sports and recreation facility is a place designed and equipped for individuals or groups to engage in physical activities, sports, exercise, and leisure pursuits.
-
B.
indoor athletic facility
An indoor athletic facility is a covered, climate-controlled space equipped with specialized areas and equipment designed to support a variety of sports, fitness activities, and physical training programs year-round.
-
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.
sports architecture division
The sports architecture division is a specialized unit focused on planning, designing, and overseeing the construction or renovation of sports facilities and venues to optimize performance, safety, and spectator experience.
-
E.
energy training facility
An energy training facility is a specialized center where individuals and organizations learn, practice, and develop skills related to energy production, management, efficiency, and safety using dedicated equipment and simulated environments.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:37 p.m.