Triple
T26033347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia University gym construction site in Morningside Park |
E647489
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proposed university athletic facility |
C6940
|
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: proposed university athletic facility Context triple: [Columbia University gym construction site in Morningside Park, instanceOf, proposed university athletic facility]
-
A.
sports and recreation facility
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.
sports and education complex
A sports and education complex is a multifunctional facility that integrates athletic venues with academic and training spaces to support both physical development and educational activities.
-
C.
college sports venue
A college sports venue is a facility owned or used by a college or university where intercollegiate athletic competitions, practices, and related events are held.
-
D.
sports facilities planning project
chosen
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.
-
E.
university sport event
A university sport event is an organized athletic competition or activity hosted by a higher education institution, involving student participants and often spectators, to promote physical fitness, school spirit, and community engagement.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:06 a.m.