Triple
T30869166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novartis Campus landscapes, Basel |
E786287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate campus landscape |
C32605
|
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: corporate campus landscape Context triple: [Novartis Campus landscapes, Basel, instanceOf, corporate campus landscape]
-
A.
campus landscape feature
chosen
A campus landscape feature is a designed or natural outdoor element—such as lawns, gardens, plazas, pathways, water features, or sculptures—that shapes the aesthetic, ecological, and social character of a campus environment.
-
B.
landscape architecture office
A landscape architecture office is a professional practice that plans, designs, and manages outdoor spaces—such as parks, gardens, campuses, and urban environments—by integrating aesthetics, ecology, and functionality.
-
C.
university campus area
A university campus area is the designated physical environment of a university, encompassing academic buildings, student housing, recreational facilities, green spaces, and supporting infrastructure where educational and social activities occur.
-
D.
landscape architecture department
A landscape architecture department is an academic unit that educates students and conducts research on the planning, design, and management of outdoor spaces and environments.
-
E.
university campus building
A university campus building is a physical structure within a university’s grounds designed to support academic, administrative, residential, or recreational functions for students, faculty, and staff.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:47 p.m.